Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
udpcommandport [2008/03/11 21:23]
sestst
udpcommandport [2009/03/21 08:55]
sestst
Line 1: Line 1:
 {{port64.png|}} {{port64.png|}}
 ====== UDPCommandPort ====== ====== UDPCommandPort ======
-The UDPCommandPort acts as a command line interface to the HomeServer. By sending UDP-packets to the UDPCommandPort you can access all objects in the HomeServer. Via the UDPCommandPort you can list all instances, get and set the attributes of the instances and call methods in the instances. You can also send events to the event hub. Command responses are sent as UDP-Packets to the sender port of the request packet.+The UDPCommandPort is part of the [[:​start|NetHomeServer]]. ​The UDPCommandPort acts as a command line interface to the HomeServer. By sending UDP-packets to the UDPCommandPort you can access all objects in the HomeServer. Via the UDPCommandPort you can list all instances, get and set the attributes of the instances and call methods in the instances. You can also send events to the event hub. Command responses are sent as UDP-Packets to the sender port of the request packet.
 The interface is primarily intended for machine-machine communication and not for human interaction. The syntax is described [[commandportsyntax|here]]. The supported commands are: //dir, create, get, set, rename, call, event//. The interface is primarily intended for machine-machine communication and not for human interaction. The syntax is described [[commandportsyntax|here]]. The supported commands are: //dir, create, get, set, rename, call, event//.
  

Personal Tools