Download TAGP Protocol Specification v1.1

Transcript
TAGP Protocol Specification
3
Doc no. 05-172 04
Protocol Messages
The protocol messages are divided in two sections, messages from client to server and
messages from server to client.
3.1
Client Messages
Sections 3.1.1 to section 3.1.9 describe messages sent from client to server.
A server always replies to client messages with a RPLY message, which is described
in section 3.2 Server Messages.
3.1.1
HELO: Setup Connection with Server
MID:
“HELO”
Message data: <protocol name>/<version>
The HELO message is used to setup a connection and it should be the first message
sent from a client to the server after the client has connected to the server. HELO is
used to verify that both client and server speak the same protocol.
Until a HELO message has been successfully received, the server does not respond to
any other messages, including unknown and corrupt messages.
Table 2 Example of a connection setup with protocol name TAGP and version 1.1
Client message
HELOTAGP/1.1\n
Server response
RPLYHELO00\n
If a server receives a HELO and implements TAGP with the stated version, it replies
with a “00”, which means that a connection is set up and that the server is ready to
communicate with the client.
Table 3 Example of a connection setup with version mismatch
Client message
HELOTAGP/1.0\n
Server response
RPLYHELO81TAGP/1.1\n
If the server receives a HELO message with a protocol or version that is does not
support, it replies with an error code that explicitly states which version of TAGP it
supports.
3.1.2
SET: Set Value to Variable
MID:
“SET ”
Message data: <variable name>=<value>
Note that the fourth character in this MID is a space character (ASCII value 0x20). SET
assigns a value to a server variable, either locally to the client or globally to all
connected clients.
© TagMaster AB
8 (41)