From: Jody Hagins (jody-boost-011304_at_[hidden])
Date: 2005-12-16 00:26:58
On Thu, 15 Dec 2005 22:26:26 -0600
Thore Karlsen <sid_at_[hidden]> wrote:
> Of course it matters. The client could sit idle for an hour before it
> sent the next request, and the server thread would be stuck in a
> blocking read waiting for data from the client, unable to service
> other clients.
This isn't the place to continue this discussion. I'll give a brief
reply, but after that, it should probably go to private email.
The server thread is not stuck. I think you are completely missing the
point (more likely, I am not clearly explaining the point). The thread
is never invoked until some amount of data was available.
> So if you can do this with blocking, synchronous I/O, why do you think
> asio exists? Why do you think people are arguing for asynchronous I/O
> in favor of synchronous I/O?
Hmmm. I think you are mixing too much here. First, you are assuming
stream-based IO, and synchronous IO implies blocking. With "record"
based IO (datagrams for IP based stacks), all the data is available, or
none is available.
Again, if you wish to continue, use private email.