Kris Maglione wrote: > wmii-3 exhibits much strange behavior with relation to reads on > /event, mainly related to the fact that it keeps a 'pending' > member for each connection structure, [...] and doesn't unset the > member once a read has completed.
Yes. This was the exact problem my patch had fixed. > wmii-4, however, buffers new events in a separate buffer for each > open Fid on /event. When an Tread comes in for one of these > Fids, it writes as much of the buffer as the clients have > requested. Therefore, no events are lost, and there are no > erratic Rreads sent. Thanks. I am glad this is finally resolved. -- Hardware: The parts of a computer system that can be kicked.
