Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jk2addict (4946)

jk2addict
  (email not shown publicly)
http://today.icantfocus.com/blog/
AOL IM: chrislaco (Add Buddy, Send Message)
Yahoo! ID: chrislaco@sbcglobal.net (Add User, Send Message)
Jabber: laco@scribblewerks.com

Journal of jk2addict (4946)

Thursday February 08, 2007
12:41 PM

Why do socket timeouts suck so much?

[ #32353 ]

This is just a general rant about certain OSs sockets implementations and the crappy software that uses them. In particular, sockets on windows suck butt imho. The connect timeout is entirely too long and overriding it is too damn complicated.

Take the TcpClient in .NET for starters. The only way to control the connection timeout is to write Async connection code. Yuk. Nothing irks me more than when software that tries to an eternal resource takes 120 seconds to timeout, dog piling the CPU and other resources cause servers to go south instantly.

What irks me even more is mapped drives and mapped My Document folders in XP. Maps those to a network file server sometime, then just take the server away. XP becomes totally useless. Stupid things like explorer and the IE address bar become non responsive. Multi tasking OS my butt.

Just another rant. That is all.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.