Argus supports protocol-independent transport interface of WinSocket 2.0 (which is currently included in Windows NT version 4.0). Using WinSocket 2.0 allows you work seamlessly with a number of transport protocols such as TCP/IP, X.25 etc., use protocol-independent symbolic host name resolution (for example, SAP, X.500 etc., not only DNS), Win32-overlapped input/output modes, shared sockets, conditional acceptance etc.
The current version of Argus supports the most widely used WAN protocol - TCP/IP. In future versions we are planning to implement support for other protocols.
In regard of WinSock 2.0 and Win32 use and the mulit-threaded program architecture, host name resolution, connection and disconnection's, input/output operations with TCP/IP are functioning as parallel processes; such way of operation provides optimal resource usage and minimum system load.
TCP/IP Daemon is the centre of control for all TCP/IP operations.
TCP/IP lines are created and disposed as a result of TCP/IP Daemon functioning. As soon as Argus detects an incoming TCP/IP connection or a new poll via TCP/IP in the Poll Manager, Daemon creates a new mailing system line and starts a mail transfer protocol. When a TCP/IP session finishes, Daemon closes the line and ends the connection.
| TCP | Accordingly to IP Nodelist standard (which is used in regions 46, 50 of zone 2), this flag is required to show that node is able to receive incoming TCP/IP connections. Argus may ignore the absence of this flag - using of IP-address instead of 'phone number is enough. |
| IFC | Raw (ifcifo) (the default port number is 60179). There is a List of BinkP nodes, coordinated Ruslan Hakurate. |
| TEL or TELNET | Telnet (the default port number is 23) |
| BND or BINKD | BinkP (the default port number is 24554) |