Search results

I'm using the synchronous method. I don't have the time to reference it now but I've read that there is no adjustment for that timeout. I've read about asynch methodologies but haven't really gotten around to wrapping my head around it. I'm on a tight schedule of projects so usually the...

cjard, The post following yours reminded me that it was a 2-connetion-per-host limit in IE that I was thinking of. But it was indeed a limit imposed in MSXML as well (which version, I don't recall, it's been a few years). My connection methodology works well, the sign is normally updated...

Yes, different socket instances in different classes. No overlapping of scope. I was catching the exception, calling .close and anything else I could find that might do the trick. The answer was to bubble the exception all the way out of the parent routine (object, method, whatever) and...

No, two different socket instances in two different classes. Create socket #1 to sign Create socket #2 to env sensor read sensor via #2 close #2 send command to sign via #1 close #1 The problem was that if there was a timeout connecting socket #2, I could not use socket #1 (or any other...

It is indeed a problem at the "other end" but I need to account for it in my code as I can't have the application just fail when there's a network disruption. This time the device is on the local LAN but that of course won't always be the case. So the code opens a socket to the sign, then...

OK, more data.... It appears that if you close ALL socket connections in the program, functionality is returned. I had the two sockets open in nested procedures. Closing the socket in the outer procedure did the trick. Still lame, tho. A good .NET wrapper to WinAPI functions should work...

I had to leave this project for a while but now I"m back to it. I tried socket.close in my Finally block, I've set the member variable to Nothing at the start of the routine that opens teh connection - all to no avail. And I'm still noticing that when a connection to one device fails, I...

Thanks for the input. I see this method is a .NET 2.0 addition. My program is in 1.1 for now (VS 2005 is actually on it's way to me as I type this) so I hadn't seen this option. I suppose it's worthy to note that the .Shutdown method should be called before .Disconnect I'll post back as...

I'm writing a VB.NET app that sends commands to an LED message sign periodically. It runs as a service. I'm using the .NET Socket library and things are working perfectly! Until there is a network disruption, that is. I'm catching and bubbling up any exceptions and that's working fine, too...