Difference between revisions of "DCE Binary Communication Protocol"

From LinuxMCE
Jump to: navigation, search
(How to create an event connection)
(How to create an event connection)
Line 14: Line 14:
  
 
>> Device sends:  
 
>> Device sends:  
 +
 
''HELLO <my_device_id> '\n'''
 
''HELLO <my_device_id> '\n'''
 +
  
 
<< To router can response with :  
 
<< To router can response with :  
''NOT IN THIS INSTALLATION IP=127.0.0.1 '\n'''
+
 
 +
''NOT IN THIS INSTALLATION IP=<device_ip_address> '\n'''
 +
 
 
or
 
or
''OK 43 IP=127.0.0.1 '\n'''
+
 
 +
''OK 43 IP=<device_ip_address> '\n'''
 +
 
 +
 
 +
>> Device sends:
 +
 
 +
''EVENT 43 '\n'''
 +
 
 +
<< To router will response with :
 +
 
 +
''OK 43 IP=<device_ip_address> '\n'''
  
 
== How to create a command connection ==  
 
== How to create a command connection ==  

Revision as of 12:50, 16 May 2007

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=<device_ip_address> '\n'

or

OK 43 IP=<device_ip_address> '\n'


>> Device sends:

EVENT 43 '\n'

<< To router will response with :

OK 43 IP=<device_ip_address> '\n'

How to create a command connection

How to serialize a message

How to serialize data

How to serialize data-grids