I solved the problem, it wasn't a threading issue at all. The problem was an oversight on my part. My message string that was being sent to the client was being handled improperly after my last change. The service performs just as it was meant to.
Also, thanks for the heads-up with the EndSend suggestion. All other callback ended their respective action with EndXXX except for the BeginSend callback, and without that call the BeginSend method would block. Thanks for your feedback, I appreciate it. On Jan 12, 6:55 am, tcomer <[email protected]> wrote: > All of my methods call the EndXXX methods in their respective > callbacks. I've turned off the Windows firewall to be sure that wasn't > causing it, and it wasn't. The service uses a System.Timers.Timer > also, so it may have something to do with that - the Elapsed event is > currently triggering the BeginSend. Thanks for the reply > > Best regards, > T. Comer > > On Jan 12, 3:30 am, Usman <[email protected]> wrote: > > > > > The way you are using sockets is called asynchronous sockets > > that is when u put any kind of request on the socket like > > connect, send and or receive it doesn't waits for the response. you > > can acheive response with corresponding end methods > > EndReceive EndConnect and EndSend Methods using IAsynResult interface > > Or If you want to use Synchronous Sockets then i woud suggest u to use > > threads to achevie auto response- Hide quoted text - > > - Show quoted text -
