Difference between revisions of "DCE Binary Communication Protocol"
From LinuxMCE
(→Introduction) |
(→How to create an event connection) |
||
| Line 9: | Line 9: | ||
The DCERouter process is listening on 3450 port. | The DCERouter process is listening on 3450 port. | ||
| − | == How to create an event connection == | + | == How to create an event connection == |
| + | |||
| + | Here is how the handshake is made for an event connection: | ||
| + | |||
| + | >> Device sends: | ||
| + | ''HELLO <my_device_id> '\n''' | ||
| + | |||
| + | << To router can response with : | ||
| + | ''NOT IN THIS INSTALLATION IP=127.0.0.1 '\n''' | ||
| + | or | ||
| + | ''OK 43 IP=127.0.0.1 '\n''' | ||
| + | |||
== How to create a command connection == | == How to create a command connection == | ||
== How to serialize a message == | == How to serialize a message == | ||
== How to serialize data == | == How to serialize data == | ||
== How to serialize data-grids == | == How to serialize data-grids == | ||
Revision as of 13:48, 16 May 2007
Contents
Introduction
A device can create a command connection and one or more event connections to the router.
The command connection is used as an incoming connection and device will use it to receive message from the router (commands).
An event connection is used by the device as an outgoing connection to notify the router about events or the deliver commands to other devices.
The DCERouter process is listening on 3450 port.
How to create an event connection
Here is how the handshake is made for an event connection:
>> Device sends: HELLO <my_device_id> '\n'
<< To router can response with : NOT IN THIS INSTALLATION IP=127.0.0.1 '\n' or OK 43 IP=127.0.0.1 '\n'
