4D v13.2TCP_Listen |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
4D v13.2
TCP_Listen
TCP_Listen
The TCP_Listen command opens a communication "socket" on the port specified by the localAddress and localPort parameters. This command does not return control back to the 4D calling method until either a connection is made or the timeout period has elapsed. Though it may seem as though this would lock up your database until a connection was made, the command is friendly to other 4D processes that may be running. This command will slice time to other 4D processes you may already have running. Most developers will want to issue this call from a method which has been spawned into its own 4D process (especially if you specify the timeout period to wait forever). The localAddress parameter contains the local IP address where the incoming connection must be made:
localPort contains the TCP port you wish to use for communication. If you pass a zero as this parameter, the command will find any unused port and pass that number back to this parameter. timeout specifies the number of seconds this command will wait for an incoming connection. A zero in this parameter will cause the command to wait indefinitely for an incoming connection. Caution should be taken when passing a zero since control will never be returned to the calling 4D process if a connection is never made. Never pass zero to this parameter in a single-process database. tcp_ID is the long integer reference to the session that was opened. This reference will be used in all subsequent TCP external calls that reference this session. Any TCP connection opened using the TCP_Listen command must be closed later using the TCP_Close command. C_LONGINT(vTCPID) |
PROPERTIES
Product: 4D
INDEX HISTORY
Modified: 4D Internet Commands 6.8.1 SEE ALSO
Appendix B, TCP Port Numbers |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||