Re: Comm API notes

On ons, 2008-09-10 at 15:45 -0600, Alex Rousskov wrote:

> Take an HttpStateData, for example. When the socket descriptor is
> closing, HttpStateData may still have a lot of work to do. The old code
> (some of which remains) assumed that comm_close is pretty much the final
> word. After that, there is no valid state to care about and no work to
> continue. That's wrong. Does this example clarify the difference between
> "stop I/O on this descriptor" and "kill this job"?

Yes, I think so.

But the direct relation you tink of didn't exist before either. Only
indirectly by close handlers.

> Hopefully, the above steps will make it easier. I have not refreshed my
> memory on overlapping I/Os and other Windows details, but I am certain
> the initial steps outlined in the notes will be required anyway.

Getting away from fd_t being an int is the most important part. The rest
is just adaptation glue..

Regards
Henrik
Received on Wed Sep 10 2008 - 21:52:49 MDT