Just adding a bit to this.
Keep in mind that both client and server need to establish a "common ground"
or "common set of rules" that they will both obey. If you want the server
side to use a persistant type of connection then the client must also
implement it. If the client is a 3rd party (ie. not your code) then you
will have to code your server to whatever "rules" the client has.. and the
same is true if the server code is not yours - you will have to code your
client to whatever "rules" the server has.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Charles Cox
VC/VB/C# Developer
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Ignacio Machin ( .NET/ C# MVP )" <ignacio.machin AT dot.state.fl.us> wrote
in message news:Oq****************@TK2MSFTNGP12.phx.gbl...
Hi,
"Macca" <Ma***@discussions.microsoft.com> wrote in message
news:A8**********************************@microsof t.com... Hi,
I am writing an app that will have a socket server to listen for and
process
data from 20+ clients. These clients will send data aproximately every
400-500ms.
I was wondering if it is possible when i have established a connection
with
a client to keep that connection open rather than opening and closing
every
400-500ms as i'd imagine there is overhead involved in this.
Is this possible?
It's possible IF the client does the same thing. if the client close the
connection you will receive a new connection request anyway
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation