The code really depends on the protocol. Unless these details are documented rigorously, at least 50% of socket development can sometimes be in discussion about exactly what the client is sending at different times. Is the client multi-threaded? Can you expect another process to connect on the same socket? How many? What does the client do if it is blocked for some period of time? What's the timeout? Does it try again? Does the client report errors on the first failure or does it retry? How often and how many times?
It's not unreasonable to ask a LOT of questions if there is limited documentation. You do not want to code in assumptions for an established protocol. Ask questions of the people who maintain the remote client code - getting to those people can take some time, but they may be the only ones who have the answers. HTH Tony Gravagno Nebula Research and Development TG@ remove.pleaseNebula-RnD.com Nebula R&D sells mv.NET and other Pick/MultiValue products worldwide, and provides related development services remove.pleaseNebula-RnD.com/blog Visit PickWiki.com! Contribute! http://Twitter.com/TonyGravagno > From: Gordon Glorfield > The only thing I'd do differently is... _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
