On Sun, 3 Feb 2002, Dan Kegel wrote:
> I'd like to know how it disagrees. > I believe rtsig requires you to tweak your I/O code in three ways: > 1. you need to pick a realtime signal number to use for an event queue Did that. > 2. you need to wrap your read()/write() calls on the socket with code > that notices EWOULDBLOCK This is perhaps the part we it disagrees with our code. I will investigate this part. The way we normally do things is have callbacks per fd, that get called when our event occurs doing the read, or, write directly. We do check for the EWOULDBLOCK stuff and re-register the event. The thing we do not currently do is, attempt to read or write unless we've received notification first. This is what I am assuming is breaking it. > 3. you need to fall back to poll() on signal queue overflow. Did that part too. Regards, Aaron