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

Eliom: Improve server to client communication #1

Open
2 tasks
balat opened this issue Feb 23, 2024 · 2 comments
Open
2 tasks

Eliom: Improve server to client communication #1

balat opened this issue Feb 23, 2024 · 2 comments

Comments

@balat
Copy link
Member

balat commented Feb 23, 2024

Tasks

@balat balat transferred this issue from ocsigen/eliom Mar 15, 2024
@balat balat added the eliom label Mar 15, 2024
@balat balat changed the title Server to client communication Eliom: Improve server to client communication Mar 15, 2024
@balat balat removed the eliom label Mar 15, 2024
@xvw
Copy link

xvw commented Mar 16, 2024

As COMET has become less and less popular over the years in favour of Server Side Events (for server-to-client communication) and WebScocket (for broadcast communication), is supporting COMET still viable? For legacy reasons?

@balat
Copy link
Member Author

balat commented Mar 25, 2024

If I'm right, what we call comet is actually long polling, (which is very close to SSE, or exactly the same according to some definitions). Websockets do not work behind a firewall as it is not HTTP. That's why we cannot rely only on websockets.

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

No branches or pull requests

2 participants