Single Interface Multiple Services Architecture
--------------------------------
These are used by all connections via port 12345:
--------------------------------

<WHOIS>ID[,ID]|0</WHOIS>

Returns Name of numeric ID or a list of IDs, or a list of everyone when the ID requested is '0'.

<WHO>
<NAME>Kyle</NAME><ID>2</ID>
</WHO>
<WHO>
<NAME>Mark</NAME><ID>1</ID>
</WHO>

Disconnects.

<COMMAND>QUIT</COMMAND>
--------------------------------

<WHEREIS>module-type[,module-type]|ALL</WHEREIS>

Returns Name, MID (Module ID), and type for modules with matching module-type, or all modules then the module type is 'ALL'.

<WHERE>
<NAME>Chat</NAME><MID>11</MID><MTYPE>CHAT</MTYPE>
</WHERE>
<WHERE>
<NAME>EchoUpper</NAME><MID>12</MID><MTYPE>ECHO</MTYPE>
</WHERE>

Disconnects.

<COMMAND>QUIT</COMMAND>
--------------------------------

These are used by CLIENT connections via port 12345:
--------------------------------
<CONNECT>
<NAME>name</NAME> <MID>ModuleID</MID> [<KEY>key</KEY>]
</CONNECT>

Returns ID, and numeric challenge-key on success. All further messages are sent to the connected module. (If multiple connections on a single NAME are used, the key is required)

<CONACK>
<ID>3</ID><KEY>10193</KEY>
</CONACK>

Connects to module.
OR
Returns reason for no connect.


<ERROR><NAME>Mike</NAME><MID>14</MID></ERROR>

(IE: NAME 'Mike' already exists, and no module with MID 14 exists.)

Disconnects.

<COMMAND>QUIT</COMMAND>
--------------------------------

<DISCONNECT>
<ID>ID</ID> <KEY>key</KEY>
</DISCONNECT>

Disconnects connected ID, when ID and challenge-key match.

<DISACK>
<ID>2</ID>
</DISACK>

Disconnects specified client.
OR
Returns reason for no disconnect.

<ERROR><ID>1</ID></ERROR>
(IE: ID '1' does not exist.)

Disconnects.

<COMMAND>QUIT</COMMAND>
--------------------------------

These are used by MODULE connections via port 12346:
--------------------------------
<CONNECT>
<Name>name</NAME> <MTYPE>Module-Type</MTYPE> [<KEY>key</KEY>]
</CONNECT>

Returns MID, and numeric challenge-key on success. (If multiple connections on a single NAME are used, the key is required)

<CONACK>
<MID>13</ID><KEY>2648</KEY>
</CONACK>

MODULE is now available for CLIENT connections.
OR
Returns reason for no connect.

<ERROR><NAME>EchoUpper</NAME></ERROR>
(IE: NAME 'EchoUpper' already exists.)

Disconnects.

<COMMAND>QUIT</COMMAND>
--------------------------------

<DISCONNECT>
<MID>MID</MID> <KEY>key</KEY>
</DISCONNECT>

Disconnects connected MID, when MID and challenge-key match.

<DISACK>
<MID>12</MID>
</DISACK>

Disconnects specified client.
OR
Returns reason for no disconnect.

<ERROR><ID>1</ID></ERROR>
(IE: ID '1' does not exist.)

Disconnects.

<COMMAND>QUIT</COMMAND>
--------------------------------

A client's connection is known to be to a specific module. Once connected, all a client's message data is sent to that module. SIMSA wraps the data to tell the module who it is from.

<_MSG>text data in XML from client</_MSG>

The SIMSA receives a wrapped message
(Clients must send message wrapped in a <_MSG> tag. MSG and PKT both have a leading '_' to prevent tag name collision in module defined tags.)

<_PKT> 
<FROM>client's ID</FROM>
<_MSG>text data in XML from client</_MSG>
</_PKT>

The module sends data out in a Packet wrapper, that SIMSA strips off, and the data is relayed to the client[s].

<_PKT>
<TO>id[,id]|!id|0</TO>
<_MSG>text data in XML to client</_MSG>
</_PKT>

(<TO> can be a single id or a comma separated list of ids.  <TO> can also be '0' to send to all connected clients or an id preceded by '!' to send to all clients excluding the specified id.)

The message will be sent to the listed clients as:

<_MSG>text data in XML to client</_MSG>
SIMSA Message Specification