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.9 Defines (SSP) TOSProvided Services for Server registration#define SSP_PSENDFILE 0x01
#define SSP_PSTATUSDISPLAY 0x02
#define SSP_PDISPLAYMESSAGE 0x04
#define SSP_PSENDMESSAGE 0x08
#define SSP_PUPLOADFILE 0x10
#define SSP_PCOMPRESSFILE 0x20
#define SSP_PCONTEXTPOPUP 0x40
#define SSP_PDISPLAYINFO 0x80
Services for Service Requesting Application Service Request
Same as when registering to the Server.
#define SSP_SENDFILE 0x01
#define SSP_STATUSDISPLAY 0x02
#define SSP_DISPLAYMESSAGE 0x04
#define SSP_SENDMESSAGE 0x08
#define SSP_UPLOADFILE 0x10
#define SSP_COMPRESSFILE 0x20
#define SSP_CONTEXTPOPUP 0x40
#define SSP_DISPLAYINFO 0x80
Data identification for Service Requesting Application Service Requestmessagebuf[4], identifies the type of data for the Server to determine
possible services.
#define SSP_TEXT 0x01
The shared memory block contains NULL-terminated ASCII text. Possible
services will be: SSP_DISPLAYMESSAGE, SSP_SENDMESSAGE (sends or
displays the text directly)
SSP_SENDFILE, SSP_UPLOADFILE, SSP_COMPRESSFILE and combinations
(sends, uploads or compresses Text as file)
#define SSP_FILENAME 0x02
The shared memory block contains Null-terminated file path and -name.
Possible services will be: SSP_SENDFILE, SSP_UPLOADFILE,
SSP_COMPRESSFILE and combinations (sends, uploads or compresses file)
#define SSP_STATUSICON 0x04
The shared memory block contains Icon data. Possible Service:
SSP_STATUSDISPLAY
This service will be started and performed without user interaction.
The server will, when receiving SSP_SRASR with SSP_STATUSICON as
dataID, send a request for SSP_STATUSDISPLAY to the SPA.
#define SSP_INFOBUF 0x08
The shared memory block contains nothing but has to be a buffer with
space for the maximum length of displayable information (determined by
the SRA) and have read and write access rights.. Possible Service:
SSP_DISPLAYINFO#define SSP_CONTEXTREQUEST 0x10
No shared memory block has to be created. This dataID indicates use of
the Context Popup Service. Possible Service:
SSP_CONTEXTThis makes clear that the SRA usually does not request a specific
service. It provides a certain type of data to the Server (and thus to
the SPA), and the Server determines which services can be used with
this type of data. In case of SSP_CONTEXT, SSP_INFOBUF and
SSP_STATUSICON there is only one possible service. The Status Display,
Display Information and Context Popup Services are usually used in
conjunction.
SRA-side definition of a data-type has the advantage that new services
can be introduced and immediately used with a new Server release,
without changes in the SRA. Also, the Server will provide the popup
menus for choosing SPA and service in context to the data
identification. For SSP_FILENAME for example, the popups could look
like this:
System Services -> Send File
Upload File
Compress File
Compress & Send
Compress & Upload
While for SSP_TEXT it could be like this:
System Services -> Send as message
Send as File
Upload as File
Compress as File
Compress & Send as File
Compress & Upload as File
AES message definitionsWe reserve the messages 4719 (0x126F) to 4739 (0x128D), messages after
0x1274 for future use.
#define SSP_SRASR 0x126F
#define SSP_SSIR 0x1270
#define SSP_SPASI 0x1271
#define SSP_SSUR 0x1272
#define SSP_SPASA 0x1273
#define SSP_SSA 0x1274