IPDaemon Component |
The IPDaemon control can be used to create TCP/IP servers running on PC's connected to a TCP/IP network. The control can handle up to 1000 simultaneous connections on the same TCP/IP port (service port). It is designed to balance the load between connections for a fast, powerful server. (NOTE: The following is a very short description. For more information, please consult the help files that come with the respective package.) |
Each instance of IPDaemon can handle up to 1000 simultaneous incoming connections. These connections are identified by a ConnectionId (a number between 1 and 1000). Most of IPDaemon's properties are array properties indexed by ConnectionId. IPDaemon's events also have ConnectionId as a parameter to identify the connection they relate to.
Our main goal in designing IPDaemon was to make it easy to use without sacrificing performance. The control has a minimum of properties, and six events: ConnectionRequest, Connected, DataIn, Disconnected, ReadyToSend, and Error.
IPDaemon can start to listen on a port by setting the Listening to True. When a remote host asks for a connection, the ConnectionRequest event is fired. At that point, the connection can either be accepted or rejected. If the connection is accepted, a ConnectionId is assigned, and communication can start. From this point on, the operation is very similar to IPPort. Data is sent by assigning the data string to the DataToSend property. The address and port of the incoming connection can be found by querying the RemoteHost and RemotePort properties.
This control requires a Winsock 1.1 compliant TCP/IP stack. This means that the Winsock stack installed in the system must have a version of at least 1.1. In particular, Windows 95, 98, and NT machines with Winsock 2.0 are fully supported.
PROPERTIES |
EVENTS |