What steps will reproduce the problem?
1. open /event
2. try to read a small buffer's worth (eg 16 bytes)
3. wait for an event that generates more than 16 bytes
4. watch as wmii returns more than 16 bytes to the client
Obviously it's not a big issue, the only reason I was using such a small read buffer was to test my code on the buffer boundary - it's unlikely to happen in practice.
Just felt this type of protocol violation is worth documenting, in case it isn't limited to just /event type files.
Original issue reported on code.google.com by sqw...@gmail.com on 14 Oct 2012 at 12:57
Original issue reported on code.google.com by
sqw...@gmail.com
on 14 Oct 2012 at 12:57