I think almost all such messages could simply use a specific callback

    that checks for a specific set of conditions.  For example, if the

    reader blocks it is simply waiting for an unblocking condition such

    as data present in the sockbuf or an EOF/disconnect condition.
    The most complex case might be something used by the atomic record

    code or the HTTP filter code, where data is present in the sockbuf but

    the reader wants to wait for more.  In that case a single field could

    be supplied, aka the disred wbytes target.
					-Matt

					Matthew Dillon

					<dillon@backplane.com>

Or, it could be waiting for *more* data in the sockbuf. How can the protocol

decide if more data arrived without knowing how many bytes the process side

thought there were in the sockbuf?
Aggelos