On Feb 26, 2009, at 2:20 PM, Fabian Rueger wrote:
Hi everyone,
Ookay, maybe I do not understand TCP/IP after all...
I am writing a server/client application; the problem is: Only one
client seems to be able to connect, but not more.
On my server, there is a serversocket set to Port X (larger than
1024).
First client connects, logs in, all is wonderful. It connects on
that port x, and keeps talking on it too.
Second client attempts to connect... and can't even get in. It's as
if he never attempted.
The server's sockets handed out are the same subclass of
EasyTCPsockets I use to connect with the clients, they just know via
a boolean property
whether they operate from a server or client side.
Which begs the question:
Can a server have multiple sockets (his serversocket and a plethora
of EasyTCP socket subclasses) operating _all_ over the same port (x),
or do I need to change the ports on the non-server sockets once the
connection is established? (To port x+1, x+2, ...x+n?)
Any comments would surely be scrutinized for content and
appropriately appreciated.
Check the value of the MaximumSocketsConnected property of your
ServerSocket object. It should be set to a value > 1 to allow
multiple connections, as I have discovered :)
Charles Yeomans
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|