Hi Markku, thank you for clearance. It seems i do exactly as you saying, but have very often server(or client) breaks communication during data transmission.
maybe should i use small Sleeps between reading from socket on server side? dima MU> Dmitry Konnov wrote: >> in Synapse TCP communication, >> who should close socket first if client request completed >> successfully, for example: >> >> Client requested a String, Server have sent the String. >> Should server at this point to wait some successful notification from >> client to close socket? MU> That pretty much depends on the protocol, though usually it is of no MU> consequence; when the request/response -part has been acted out, the MU> participants are usually free to continue as they wish. Personally, I MU> generally close the socket (on the server side) as soon as I've sent all MU> the data I'm supposed to send (and it is not expected that the client MU> would write anything more to me) ... and same on client; when I've read MU> all I'm expecting, I close the socket. -- Best regards, Dmitry mailto:konno...@mail.ru ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ synalist-public mailing list synalist-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synalist-public
