Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web sockets vs SSE #4

Open
scottjbarr opened this issue Dec 4, 2020 · 2 comments
Open

Web sockets vs SSE #4

scottjbarr opened this issue Dec 4, 2020 · 2 comments

Comments

@scottjbarr
Copy link

scottjbarr commented Dec 4, 2020

The documentation for the "Push Notifications" endpoint says,

Subscribe to push notifications using web sockets.

The use of web sockets requires libraries/packages on top of HTTP.

Given that the API is exposed over HTTP, have you considered Server Sent Events (SSE), which work natively with HTTP without extra tooling? SSE even works for relatively simple tools like the curl command line client.

See https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events

@Danconnolly
Copy link
Contributor

I think thats a good point but I'd rather see it as an extension to this spec. I dont want to crowd the spec with various implementation technologies.

@rt121212121
Copy link

SSE does not support binary messages and has other limitations. We looked at using it for ElectrumSV's client-server connections and it was not usable. ElectrumSV's server aims to support both binary and text notifications, depending on client choice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants