Tuesday, June 28, 2005

WSAEWOULDBLOCK

I've been working on the new networking code for some time now, fighting a number of integration issues with the new remote routing infrastructure. While extremely powerful, it is also very complex to debug in a systematic way.

My illness didn't help any on the progress front. So anyway, today I finally got a chance to spend some good time going over the code. During one of my breaks, I happened to read this post over at Project Aardvark, which I have been following (yes, I am a Joel on Software fanboy).

It turns out, I wasn't checking for WSAEWOULDBLOCK either. Finding the problem still took some serious effort. I'll explain more tomorrow. Right now, I am going to bed.

Sunday, June 26, 2005

Bronchitis is no fun. Spent Thursday night - ALL Thursday night, vomiting. I am only now feeling myself.

What this really means is the loss of 3-4 days of productive work which I can ill afford. I guess it just means a few more late nights.

Hopefully, I will have more to talk about this week.

Question - does the CLOSE_WAIT state suck, or is it just me. As far as I can tell, it means waiting however long your OS has set the timeout before you can relaunch your application.