Frame max_payload_size and fragmentation #46
Comments
Fragments are too low level for the user to know about them. Imagine you received a JSON message in fragments, you don't want user to deal with fragments, next_bytes should return the data that is parsed later by the user. Don't you think so? |
Ah, meanwhile I realised that I wonder then what the use is of the |
|
I think I implemented it because one of the WebSocket RFCs suggested controlling the payload size on the software level. Not that sure though... :) |
Okay, it makes sense this way, thanks :) I got around it by implementing my own fragmentation routine, should hopefully do what it has to. |
Not sure if this is a bug or a truly intended behaviour, but I was really surprised to find that when P:W:Frame runs into the payload limit, it does not attempt to make multiple fragments but just dies. There also doesn't seem to be an obvious way to ask P:W:Frame to create a handful of frames that are continuations of each other (preferably with the payload per frame limited to a certain size). Supposedly,
next_bytes
does things to the fragments array, but I only ever seem to get""
out of it.The text was updated successfully, but these errors were encountered: