$Date: 2005/10/28 11:33:36 $
$Revision: 1.26 $
-- Initialize the protocol.
-- Carriage return character code
-- (From EM_NETWORK_CONSTANTS)
-- Used for listening on all network interfaces
-- (From EM_NETWORK_CONSTANTS)
-- Used as destination when sending a message to all clients
-- on a subnet that allows broadcasts
-- (From EM_NETWORK_CONSTANTS)
-- Used for listening on all network interfaces
-- (From EM_NETWORK_CONSTANTS)
-- Line feed character code
-- (From EM_NETWORK_CONSTANTS)
-- Highest valid value for a socket port
-- (From EM_NETWORK_CONSTANTS)
-- Maximum size of a UDP packet
-- (From EM_NETWORK_CONSTANTS)
-- Lowest valid value for a socket port
-- (From EM_NETWORK_CONSTANTS)
-- max serialization count
-- (From EM_NETWORK_CONSTANTS)
-- Set max_serialization_count to a_count.
-- If UDP is used this value should be *less* than Max_udp_packet_size.
-- (From EM_NETWORK_CONSTANTS)
-- Set the handler that is called if updated data from a client arrived.
-- Arguments that are passed to the event handler:
-- time: INTEGER
-- object ID: INTEGER
-- serialized object: STRING
-- Parse client message and fire the object received event.
-- Create a new message and make it available in last_message.
-- Correction factor
-- How much weight do you want to give the new measured time compared to the old value?
-- Use a reasonable value in general not too big.
-- A value of 1 means that you well completely take the new measured time.
-- A value of 0 means that you don't give any value to the new measured time.
-- Enable time sync
-- Is this a time master?
-- In a client/server architecture you may elect the server to the time master.
-- Is time synchronisation enabled?
-- Last UDP packet that was created by create_packet
-- Time sync request event
-- Time sync response event
-- Send a time sync request.
-- The request will be sent to the group which is set by the feature set_time_sync_group.
-- set correction_factor to a_factor
--Sset time_sync_period to a_period_in_ms
-- set time_sync_group to a_group
-- Time in miliseconds
-- Group used for time synchronisation.
-- How many miliseconds should be waited until the next sync request is sent?
The protocol that is used for network communication.
This is the lowest layer in the MP framework, just on top of the
actual sockets.
Message format:
Header:
Message prefix: STRING, 5 bytes (see message_prefix)
Version: INTEGER_8, 1 byte (see version)
Time object: STRING
Data (may be repeated):
Object ID: INTEGER, 4 bytes
Data: STRING
Short:
[PREFIX|VERSION|[ID|DATA]*]