Hello,
Is there a means by which a handler registered with set-io-handler can be "deactivated" so that it isn't considered in the fd set being checked and "reactivated" later to be put back into the fd set? I ask because I might not have access to the function which I want associated, say with a write handler, but when the buffer the write handler is writing is empty. If the write handler is always activated on an empty buffer solely because it is in the write handler callback, then that is a performance problem.
Thank you.
-pete
On Sun, 2010-01-31 at 20:15 -0600, Peter Keller wrote:
Hello,
Is there a means by which a handler registered with set-io-handler can be "deactivated" so that it isn't considered in the fd set being checked and "reactivated" later to be put back into the fd set? I ask because I might not have access to the function which I want associated, say with a write handler, but when the buffer the write handler is writing is empty. If the write handler is always activated on an empty buffer solely because it is in the write handler callback, then that is a performance problem.
Currently there's no way to do that
-
Peter Keller -
Stelian Ionescu