These are chat archives for fanout/pushpin

5th
Nov 2016
lars
@larshelg_twitter
Nov 05 2016 05:14
@jkarneges Thanks for the quick reply. Yes i got the sockjs route working with the config changes. The websocket handshake is failing though. Is pushpin implementing the sockjs server spec?
lars
@larshelg_twitter
Nov 05 2016 05:48
The only reason for trying out sockjs is because of problems with websocket (firewalls etc) and then it seems like a good option to have fallback to http streaming. Do you mean to have a seperate websocket API and a seperate http stream api? Wouldnt it be better if the consumers dont have to choose but that the streaming technology is hidden for them by using a fallback solution?
Justin Karneges
@jkarneges
Nov 05 2016 19:10
@larshelg_twitter yup pushpin's sockjs implementation supports websocket. what pushpin version and what error are you seeing?
Justin Karneges
@jkarneges
Nov 05 2016 19:16
most API contracts are based on simple network interactions. sockjs is somewhat complex and you'd probably have trouble documenting it as a network interaction, and instead you'd probably end up having to tell your user to use a sockjs client library
if you offer a client sdk of your own, what you could do is have that thing use sockjs to connect. this way users of your sdk don't have to think about protocol