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
Previous revision
tcpcommandport [2009/03/21 08:54]
sestst
tcpcommandport [2018/11/03 02:59] (current)
Line 1: Line 1:
-{{port64.png|}}+{{::server:port64.png?nolink|}}
 ====== TCPCommandPort ====== ====== TCPCommandPort ======
 This module is a part of the [[:​start|NetHomeServer]]. The TCPCommandPort acts as a command line interface to the HomeServer. By connecting a telnet session to the TCPCommandPort you can access all objects in the HomeServer. Via the TCPCommandPort 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. This module is a part of the [[:​start|NetHomeServer]]. The TCPCommandPort acts as a command line interface to the HomeServer. By connecting a telnet session to the TCPCommandPort you can access all objects in the HomeServer. Via the TCPCommandPort 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.
-The interface is primarily intended for machine-machine communication and not for human interaction. It is used by the external GUI tool "​HomeClient"​. The syntax is described [[commandportsyntax|here]]. The supported commands are: //dir, create, get, set, call, rename, event, subscribe, quit//.+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, call, rename, event, subscribe, quit//.
  
 ===== Attributes ===== ===== Attributes =====

Personal Tools