Incease maxPayloadLength upper limit and/or allow 0 (limitless)

[Zabrane]

My uWebSockets.js app daily handles large amount of data (10-35GB per conn) with no issue.
One of my colleagues tried to increase the maxPayloadLength to 100GB for stress testing but it didn't work. Apparently, there's a 50GB upper bound limit.

 maxPayloadLength: 100 * 1024 * 1024 * 1024 // failed

Is there any reason for that?

@alexhultman two suggestions if you don't mind:

1. allow maxPayloadLength to take value 0 (no limit) and let the user handle the limit logic on his side
2. increase the default maxPayloadLength to a much larger value: for example 100TB (see websocket-frame-size-limitation)

[ghost]

If you want to transfer hundreds of GB you really shouldn't use one single WebSocket message. Use streaming HTTP and you can cut your memory usage in half at least?

[Zabrane]

@alexhultman what maxPayloadLength is for? Is it a limitation:

1. per message
2. per all messages inside 1 connection
3. for all ongoing connections

[hst-m]

Docs for maxPayloadLength say per message

Maximum length of received message. If a client tries to send you a message larger than this, the connection is immediately closed

[Zabrane]

Thanks for the pointer @hst-m

[Zabrane]

@alexhultman our service is WebSocket based. I'm afraid the Streaming won't help.

Anyway, i can close the issue. Thanks guys