You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 28, 2021. It is now read-only.
As it stands, a given WebSocketFrame's ByteList often contains a larger length than is required for it's headers and payload, due to the fact that the ByteList automatically grows by its growthStepSize to accommodate added bytes, 10 more byte 'slots' may be tacked on even when we already know the final size of the frame, which may only require 3 of the 10 new 'slots'.
The text was updated successfully, but these errors were encountered:
- Functionality Changes
- `ByteList.java`
- Added `resizeToLength()` method to eventually address issue #2.
- Modified `getDebugInfo()` to used `System.lineSeparator()`.
- `WebSocket.java`
- Added an inner enum, `State` and related changes.
- Modified `generateName()` to use a `StringBuilder`.
- `WebSocketFrame.java`
- Added an inner enum, `Type` and related changes.
- `WebSocketControlFrameType.java`
- Removed.
- `WebSocketDataFrameType.java`
- Removed.
- `WebSocketFrameType.java`
- Removed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As it stands, a given
WebSocketFrame
'sByteList
often contains a larger length than is required for it's headers and payload, due to the fact that theByteList
automatically grows by itsgrowthStepSize
to accommodate added bytes, 10 more byte 'slots' may be tacked on even when we already know the final size of the frame, which may only require 3 of the 10 new 'slots'.The text was updated successfully, but these errors were encountered: