🚀 go-pugleaf

A server socket is one that listens on a specified port.  When a client
makes a connection on that port, it starts a unique conversation between it
and the server.  At that point, you can send whatever you like up and down
the pipe as long as the client and the server agree on the data format.
There will never be any conflict between one client and another.  There is
nothing preventing you from changing the data format to a byte stream for
raw binary data and then switching it back again.

The problem you will have in spawning a second server socket is this:
suppose both client 1 and client 2 are instructed to make a connection on
that socket.  Client 1 is told first, 100ms before client 2.  However,
client 2 is faster and establishes the connection to the second server
socket.  Your server thinks it's talking to client 1 because that's the one
that was told to initiate contact first.

Your best bet is to use a single dedicated connection for your session.

-- 
Check out our latest white papers at
http://www.datadevelopment.com/papers/index.html

BladeNET Scores With Borland Enterprise Tools
Team Development with JBuilder and Borland Enterprise Server

Dolphin Data Development Ltd.
http://www.datadevelopment.com/

"Alan Shiers" <ashiers@hfx.eastlink.ca> wrote in message
news:3EEA1B0B.F96AB3D@hfx.eastlink.ca...
>
> > What do you mean by "set to the same Port Number"?  Are you talking
> > about ServerSockets or client Sockets?  Perhaps if you posted some
> > code, it would be a little more clear what you are doing.
>
> Yes, I'm referring to ServerSockets.
> Conceptually speaking this is all I'm trying to accomplish:
>
> I want one primary ServerSocket open with DataInputStream and
> DataOutputStream classes connected to it, and remains listening to the
> Port specified in the application, and for the duration that any Client
> may be connected. Then, a separate secondary ServerSocket, which only
> gets activated, on the fly, with BufferedInputStream and
> BufferedOutputStream classes connected to it.
>
> The idea being that, the primary ServerSocket is used only to send
> integer values (representing Constants defined in the application) back
> and forth between the server app and the Client app. And the secondary
> ServerSocket is used only to upload/download files at the byte level
> only.
>
> So, the question remains, will there be a conflict of data transfer if
> both ServerSockets are set to the same IP address and on the same Port
> Number?  Is it better to at least have each ServerSocket set to
> different Port Numbers to prevent conflict of data transfer?
>
> Alan