tcpcommandport
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
tcpcommandport [2008/03/06 20:11] – sestst | tcpcommandport [2018/11/03 02:59] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{port64.png|}} | + | {{::server:port64.png?nolink|}} |
====== TCPCommandPort ====== | ====== TCPCommandPort ====== | ||
- | 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 [[: |
+ | 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 ===== | ||
- | * ListenPort | + | |
+ | * **MessageCount** //[get]// Number of processed commands. | ||
+ | ==== See also ==== | ||
+ | [[CommandPortSyntax|Command Port Syntax]], [[UDPCommandPort]] |
tcpcommandport.1204830673.txt.gz · Last modified: 2018/11/03 02:57 (external edit)