Topic : TOS - das Betriebssystem Author : Version : tos.hyp (5. März 2013) Subject : Programmieren/Atari Nodes : 3001 Index Size : 93602 HCP-Version : 5 Compiled on : Atari @charset : atarist @lang : @default : Titel @help : @options : +g -i -s +x +zz -t4 @width : 70 View Ref-File15.10.13 Glossary TOS SRA Service Requesting Application. This means the application that sends SSP_SRASR to the Server to request use of a service. SPA Service Providing Application. This means the application that receives SSP_SSIR from the Server to indicate that an SRA has requested a service. All SPAs have to register with the SSP-Server. Service is a certain part of an applications functionality or capability that can be provided to, and used by, other applications using SSP. Generalized types of services are hardwired into the SSP-Server. See SSP services. IRS Immediate Response Service. This means a service that requires virtually immediate response to SSP_SSUR from the Server, with SSP_SPASA. DRS Delayed Response Service. This means a service that requires response to SSP_SSUR from the Server with SSP_SPASA not after performing the service has started, but after performing the service has been completed (e.g. compressing files). Invisible Service This means a service that is usually triggered automatically by the SRA without requiring user interaction. See Status Display Service. Interactive Service This means a service that is usually triggered by the SRA from a user action. See Send File Service. Server Registration All SPAs have to register with the SSP-Server before they can provide and perform any services. Registration should be done once on program installation and every time the SPA starts up. See SSP Server registration. Server or SSP-Server Application running in the background that receives and sends messages from and to SPAs and SRAs. All communication between SPAs and SRAs has the SSP-Server as mediator. See What is the SSP-Server? Message in these documents refers to an AES message received by evnt_mesag (or evnt_multi, respectively). The communication in SSP is based on AES messages. See SSP messages. Server debug mode If the environment variable SSP_SERVERDEBUG is defined (!) the Server will log all activity (service requests, message-buffers, shared memory addresses and -files, etc.) to sspdebug.log in the Server application directory, and output the same information in a window, including suggestions on how to fix possible bugs.