Hi all, For testing correctness and performance of a customized FedOne server, I wrote a testing utility that acts like many clients connecting and typing to waves at the same time.
I ran it agains "vanilla" FedOne for comparison and found an issue there. The issue reveals itself with the error: java.lang.IllegalStateException: Payload (35181 bytes) too large for buffer (32768 bytes) It happens when I fire up a ClientBackend and open a wavelet that had lots of activity in the past (somewhere between 150 and 200 deltas). The deltas are sent from the server to the client 1 by 1 (not using snapshotting feature) Individual deltas (protobuf messages) are way below 32k, but -as I read the code- SequencedProtoChannel does not try to parse messages (and find out they are <32k) if the channel has >32k waiting. Is there a reason for this behavior? Would changing the buffer size help or just postpone the problem? Thanks, Mathijs -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
