How to handle WebSockets? -> WebSockets fucks up the protocol handling on the server side.
WS messages tunneld inside WS messages are wrong pared/handeld in the backend.
[backend] <-> [websockets] <-> [connector] <-> [device]
|----------- WAN ----------|----------- LAN ---------|
Because we use WebSockets as streams/transportation, if we connect to a device interface via WebSockets, this messages get misinterpreted on the backend.
A possible solution would be to "wrap" everything.
How to handle WebSockets? -> WebSockets fucks up the protocol handling on the server side. WS messages tunneld inside WS messages are wrong pared/handeld in the backend.
Because we use WebSockets as streams/transportation, if we connect to a device interface via WebSockets, this messages get misinterpreted on the backend.
A possible solution would be to "wrap" everything.