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
Due to the repetitiveness of the data, gzip compression would reduce this from 704 bytes to 202 bytes.
Implementation
If enabled in the configuration, the Gorilla WebSocket updater should have the EnableCompression flag set to true.
Since the Gorilla WebSocket Compression feature is still flagged as Experimental, Resgate should have compression disabled by default.
An option should be added to the configuration file. Since http compression might later be added, the option name should clearly indicate it is for the WebSocket:
wsCompression(boolean)
Flag telling if WebSocket per message compression (RFC 7692) is enabled. Example:false
The text was updated successfully, but these errors were encountered:
Story
Resgate should have an option to enable WebSocket message compression.
This would effectively counter the bloated message size when receiving resources with multiple models containing the same key names.
Example
A collection of reference to models could look like this:
Due to the repetitiveness of the data, gzip compression would reduce this from 704 bytes to 202 bytes.
Implementation
If enabled in the configuration, the Gorilla WebSocket updater should have the EnableCompression flag set to true.
Since the Gorilla WebSocket Compression feature is still flagged as Experimental, Resgate should have compression disabled by default.
An option should be added to the configuration file. Since http compression might later be added, the option name should clearly indicate it is for the WebSocket:
wsCompression (boolean)
Flag telling if WebSocket per message compression (RFC 7692) is enabled.
Example:
false
The text was updated successfully, but these errors were encountered: