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

Tyranid client subscriptions use polling instead of websockets #125

Open
yangchristian opened this issue Dec 18, 2017 · 0 comments
Open
Assignees

Comments

@yangchristian
Copy link
Member

yangchristian commented Dec 18, 2017

If you look at network traffic, client subscriptions use polling:
image

I think we may want to change the socket.io server setup call to use listen() instead based on the following stack overflow threads:

We might also need to make sure the client transport option is set to use sockets: https://stackoverflow.com/a/41396396/1406819 (although it seems odd that it'd default to polling)

Looks like even though the option prioritizes polling, there is a default behavior to upgrade to sockets: socketio/socket.io-client#883

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

No branches or pull requests

2 participants