[ENet-discuss] Multiple peers using a single server connection

[Steve Williams]

With TCP connections, such as HTTP, the server is listening on port 80, but when it accepts a connection, the endpoint on the server is not port 80 any more.  It gets farmed out to a free port and the server continues listening on port 80.

With UDP, which is what ENet uses, the server listens, reads and sends packets from only the specified port.

Steve 'Sly' Williams
Lead Programmer
Krome Studios

From: enet-discuss-bounces at cubik.org [mailto:enet-discuss-bounces at cubik.org] On Behalf Of steve at stamm.com
Sent: Friday, 20 June 2008 2:12 AM
To: enet-discuss at cubik.org
Subject: [ENet-discuss] Multiple peers using a single server connection


I have a need to set up a connection to an eNet server and allow several peer connections to share the port that is connected to the server. I know that eNet isn't exactly set up for this but does anyone have an idea as to the best way to implement such a setup? It would work like port 80, the http port. I can have multiple browsers open and prowsing even though they are from different vendors but they all are using port 80.



Thanks,



Steve

________________________________



This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cubik.org/pipermail/enet-discuss/attachments/20080620/f49313cb/attachment.htm>