Separate endpoints for websockets and fallback transports
clastr opened this issue · comments
We have a use case where we have a cluster of sock.js-capable servers behind load balancer and each of nodes need to have 2 endpoints:
- for websockets transport - without stickyness - handled by our own code
- for rest of the fallback transports - with stickyness - handled by one of sock.js server implementations in the same node
Is this use case already supported?
I understand, that sock.js javascript client library need to be modified to choose to which endpoint to connect?
cc: @oribrost , @nivertech
If you have a sane load balancer just forward requests to "/prefix///websocket" to whatever you want.
Additionally, please take a look at the "raw websocket" url in the sockjs-client README.
Was this helpful?
we testing it today
Closing, feel free to reopen if you have any more issues.