Owner`s manual

Terminal Native Command Reference
HTTP / Low Level ASCII script sequences
Planning
Local, PC-based programs can be written in any language that has some way to access TCP communication
on your LAN and over the Internet.
Web based server applications can be written in any language that can access a database backend and serve
HTTP web pages, such as PHP, ASP, Pearl, Python,etc.
Host - Terminal Communication Programming
All messages sent to a Terminal are in the form of a simple HTTP web page. All messages received from a
Terminal are in the form of a standard HTTP page request.
Data coming from and going to a Terminal is embedded in the data portion of the HTTP structure as defined
below.
The Terminal initiates all communication. Connection is kept open until server replies and then closed.
Terminal Output Definition
This is page request sent to web server, either a Connection Host or a web-based Application Server.
Sample:
POST /connect/terminal.php HTTP/1.1
Host: www.worthdata.net
Keep-Alive: 115
Connection: keep-alive
Content-Length: 56
Content-Type: application/x-www-form-urlencoded
user=peter&pswd=test&termID=t1&serverID=s1&termdata=%0F
(blank line)
Explanation:
This is a standard “page request”, just like what would be sent by your web browser program. It is
equivalent to
www.myserver.com/termrouter/terminal.php?user=peter&pswd=test&termID=t1&serverID=s1&termdata=%0F
The HTTP “header” portion is the first 6 lines; could be more or less, but is always followed by a blank line.
The actual data starts with “user=...” and is always followed by a blank line that terminates the HTTP
packet.
Most programming environments will have tools to help you break out the variables contained in the data:
user
pswd
66