Re: Comm API notes

2008/9/11 Alex Rousskov <rousskov_at_measurement-factory.com>:
> Here is a replacement text:
>
> The comm_close API will be used exclusively for "stop future I/O,
> schedule a close callback call, and cancel all other callbacks"
> purposes. New user code should not use comm_close for the purpose of
> immediately ending a job via a close handler call.

Yup.

(As part of another email) I'd also make it completely clear that the
underlying socket and IO may not be immediately closed via a
comm_close() until pending scheduled IO events occur; and that the
callers should be prepared for the situation where the underlying
buffer(s) and other resources must stay immutable until the completion
of the kernel-side stuff.

This is partially why I wanted explicit notification, cancellation or
not, so the owners of things like buffers would know when they were
able to modify/reuse them again - or the "immutable" semantics must be
enforced some other way.

Adrian
Received on Thu Sep 11 2008 - 04:31:17 MDT