before with:
C++, WS2003-2000 for server, XP Pro-2000-WS2003 for client, It's a portion of our product, we do our own 'highly scalable' streaming video (client, server, compression) only it turns out to (a)not be scalable because of some really stupid poo and (b)not be good at streaming video from wireless cameras because they have lots of network interruptions and this piece of poo wasn't coded to be able to 'reconnect' (interrupts look like timeouts) and because it uses IOCP it isn't very open to the idea of 'reconnection' and you can't pull things out of IO completion ports (you have to close handles to have IOCP dump 'keys' but because of the inherently *very* threaded nature of IOCP and the fact you don't have access to the IOCP's own worker threads, just your own, you have to be careful dumping things.) I was just really pissed to discover that we use this archaic, albeit very scalable, piece of technology and jump through lots of hoops to do so only to find out that its benefits are totally invalidated by a stupid f***er who decides to block threads in the streaming server code synchronously waiting for a frame of video to fill up. Quite literally it does the following:
{ lnResult = recv( mhConnectionSocket, blah, blah); }
Not a problem if you're dealing one connection (or a couple, really) but a nightmare when you're supposed to be handling hundreds! LOL.
It was just a very long day yesterday, and it has been a very long series of days lately, and I need a vacation back to Liverpool.
WTH
