Socket Server Node

From PresenceWiki
Revision as of 09:50, 17 October 2012 by Mattpryor (Talk | contribs)

(diff) ←Older revision | view current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

http://www.international-presence.com/wikidocs/images/socket_node_server.png

The Socket Server Action node allows Presence to act as a TCP/IP socket server and communicate with remote or local clients. When the socket server receives a connection and completes the data exchange it continues along the task execution path.


http://www.international-presence.com/wikidocs/images/socket_server_dialog.png

  • Name : This is the name you would like to give to this node
  • Label : The identifies the socket server and allows it to be referenced. Ideally this should be unique per socket server.
  • Address : This will always be "localhost" for the server.
  • Port : The port that the socket server should listen on.

Socket Actions

This specifies the protocol for communication. A socket server can read and write data and disconnect the client and / or the server.


Task Elements : Action Task Elements : Socket Server Node

Send Email | Send SMS | Send Fax | Broadcast Messages
Read Text File | Read Binary File | Write Text File | Write Binary File | Parse File Action
Rename File | Copy File | Delete File | Parse File Action
Generate Bar Code | Read Bar Code
Dynamic Task Call | Call Native Program | FTP Upload | Scorecard Collector | Create Graph | AS400 Action
Socket Client Action | Socket Server Action
JMS Producer | JMS Consumer


Task Elements | Resources