I have been trying to integrate Dave Bailey's bsdproxy with an experimental transport protocol (substitutes for TCP and preserves same API semantics). However, I can't seem to trigger a read event with the new protocol-- the client side socket buffer fills up with data but bsdproxy never gets a read event. I have been able to use simpler proxies (ones that basically pipe between descriptors) successfully.
Is there anything special that needs to be done at the transport layer to trigger a kevent read? My protocol calls sorwakeup() at the appropriate times-- I had thought that would be enough and that kqueue would be indifferent to the underlying transport protocol implementation. Nothing seems apparent in the TCP code, however. Tom To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
