note 56328 deleted from function.socket-listen by googleguy
| From: | googleguy@php.net | Date: | Tue, 22 Oct 2013 06:53:35 +0000 |
| Subject: | note 56328 deleted from function.socket-listen by googleguy | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-196694@lists.php.net to get a copy of this message | ||
Note Submitter: lewislp at yahoo dot com
----
socket_listen() cannot be used for UDP communications as discussed below.
In addition, the example below discusses UDP connections, which only exist if the application
manages them through a state table (the OS does not create a UDP connection upon receiving a
datagram). Having a function named socket_connect() that determines the remote IP and port only
confuses the matter by giving the indication of some sort of connection handshake between two hosts.
Rather, socket_connect() only specifies the remote IP and port used by subsequent socket_send()
calls. You can achieve the same effect by skipping socket_connect() altogether and specifying the
remote IP and port in socket_sendto() calls.
If you find yourself writing a connection-based protocol on top of UDP, consider using TCP. If your
application requires streaming data of some sort, use TCP to manage connections and control
messages, and UDP to handle the streaming data (H.323 is an example of a suite of TCP and UDP
protocols working in conjunction).