Currently WebSocket API and WebSocket Plug-in uses the standard WebSocket API. However I think Gorilla is more feature rich and is widely used.
I have several reasons to try implementing Gorilla-based WS API in SensorBee:
- Recent versions of Google Chrome fragments WS packets for large messages. When sending long BQL queries from Chrome via WS API, SensorBee fails to handle it. Gorilla docs says it supports fragmented packets.
- Gorilla also supports compression (though it is experimental) which may increase the performance.
Are there any reasons to use standard library?
Currently WebSocket API and WebSocket Plug-in uses the standard WebSocket API. However I think Gorilla is more feature rich and is widely used.
I have several reasons to try implementing Gorilla-based WS API in SensorBee:
Are there any reasons to use standard library?