Sorry guys, but I think you are completely wrong. On Wed, Sep 20, 2006 at 02:24:53AM -0700, Suraj N. Kurapati wrote: > wmii-4 simply returns the next event and closes the read request. > > wmii-3.1 returns the next event, closes the read request, and > continues to send new events as they occur (even though the request > was already closed).
NO no no. The behavior of reading /event in wmii-3 and wmii-current is equal. Reading /event means reading a file which never ends, thus the read is blocking until a new event occures. I think you misunderstand the code, though it's true that my wmii-3.x fs.c implementation is a nightmare. Kris' wmii-4 fs.c implementation is much better in many decisions. However, on the 9P level there is no difference!!!! > Now, because wmii-4 does not continually stream events to you (even > after the read request was finished), there is a possibility that > you may miss out on events. That is, when you (1) read an event, (2) > process it, and (3) read another event, you may have missed new > events that occurred while you were processing the old one. Sorry, this is not true. No events are lost. Maybe there is a bug somewhere else, but events are send to all connections which have opened /event. Please don't consider using arbitrary crap like bus protocols. NO EVENT IS LOST. If so, the problem must be somewhere else. Regards, -- Anselm R. Garbe ><>< www.ebrag.de ><>< GPG key: 0D73F361 _______________________________________________ [email protected] mailing list http://wmii.de/cgi-bin/mailman/listinfo/wmii
