The issue is about making it possible to use a configured *kite.Kite with "mixed" kites, where one of them uses websocket and other xhr transport.
Right now one needs to configure the transport explicitly for each endpoint - if wrong transport is used, it would make the communication fail (e.g. websocket for xhr-only endpoints).
The idea is to try to connect over websocket and then fallback to xhr.
Couple of bonus points:
research if go-sockjs xhr implementation could be used instead maintaining our own
The issue is about making it possible to use a configured
*kite.Kite
with "mixed" kites, where one of them uses websocket and other xhr transport.Right now one needs to configure the transport explicitly for each endpoint - if wrong transport is used, it would make the communication fail (e.g. websocket for xhr-only endpoints).
The idea is to try to connect over websocket and then fallback to xhr.
Couple of bonus points: