|Don't ask to ask, just ask|
They have a similar base
Mine does a two step between accept and read, a client CAN create the connection and wait a bit before writing, so mine wont block there. But in general http: clients shouldnt matter.
His has a better read, the way i commonly use it is a lot like his, but i just collect data, then have another loop that looks for completed lines so i dont block on the \n. IN both of these examples we block on the
I added a cmd lookup table for what to execute
I only look at the first line sent.
I added the /null command to show you what might happen if you dont send anything back
In reply to Re^7: Adding simple HTTP controls to existing code