Sack Library Documentation
sack::msg::protocol Namespace

Defines structures and methods for receiving and sending messages. Also defines some utility macros for referencing message ID from a user interface structure.

The following table lists structs, records, enums in this documentation. 
The following table lists types in this documentation. 
The following table lists macros in this documentation. 
This is macro sack::msg::protocol::INTERFACE_METHOD. 
This is macro sack::msg::protocol::LOWEST_BASE_MESSAGE. 
This is macro sack::msg::protocol::MSG_DispatchPending. 
Dispach Pending - particularly display mouse event messages needed to be accumulated before being dispatched this event is generated when no more messages have been received. 
skip a couple messages so we don't have to recompile everything very soon... 
this is a fun thing, in order to use it, undefine MyInterface, and define your own to your library's interface structure name (the tag of the structure) 
Mate ended - for the client, this means that the server has become defunct. For the server, this means that a client is no longer present. also issued when a client volentarily leaves which in effect is the same as being discovered gone. param[0] = Process ID of client disconnecting result_length = INVALID_INDEX - NO RESULT DATA, PLEASE! 
finally - needed to define a way for the service to actually know when a client connects... so that it may validate commands as being froma good source. also, a multiple service server may want this to know which service is being loaded. params + 0 = text string of the service to load on return result[1] is the number of messages this routine expects. result[0] is the number of events this service may generate 
This is macro sack::msg::protocol::MSG_OFFSET. 
This is macro sack::msg::protocol::MSG_ServiceLoad. 
This is macro sack::msg::protocol::MSG_ServiceUnload. 
Service is about to be unloaded - here's a final chance to cleanup before being yanked from existance. Last reference to the service is now gone, going to do the unload. 
no defined mesasage fo this 
This is macro sack::msg::protocol::MSG_UserServiceMessages. 
this is the techincal type of SYSV IPC MSGQueues 
This is macro sack::msg::protocol::MSGQ_ID_BASE. 
this will determine the length of parameter list based on the first and last parameters. 
This is macro sack::msg::protocol::ServerFunctionEntry. 
This is record sack::msg::protocol::buffer_len_tag. 
result of EventHandlerFunction shall be one fo the following values... EVENT_HANDLED 0 - no futher action required EVENT_WAIT_DISPATCH 1 - when no further events are available, please send event_dispatched. this Event was handled by an internal queuing for later processing. 
This is record sack::msg::protocol::server_event_messages. 
This is record sack::msg::protocol::server_failure_messages. 
This is record sack::msg::protocol::server_function_entry_tag. 
This is record sack::msg::protocol::service_messages. 
This is type sack::msg::protocol::BUFFER_LENGTH_PAIR. 
This is type sack::msg::protocol::SERVER_FUNCTION. 
MsgID will be < MSG_EventUser if it's a system message... MsgID will be service msgBase + Remote ID... so the remote needs to specify a unique base... so ... entries must still be used... 
This is type sack::msg::protocol::EventHandlerFunctionEx. 
This is type sack::msg::protocol::EventHandlerFunctionExx. 
params[-1] == Source Process ID params[-2] == Source Route ID 
This is type sack::msg::protocol::server_function_table. 
server functions will return TRUE if no failure server functions will return FALSE on failure FAILURE or SUCCESS will be returned to the client, along with any result data set. native mode (unspecified... one would assume stack passing, but the world is bizarre and these are probably passed by registers. 
This is type sack::msg::protocol::server_message_handler_ex. 
Created with a commercial version of Doc-O-Matic. In order to make this message disappear you need to register this software. If you have problems registering this software please contact us at
Copyright (c) 2000+. All rights reserved.
What do you think about this topic? Send feedback!