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

Emit user activity data using a volatile socket event to prevent unnecessary buffering of non-critical data. #9344

Closed
mkahvi opened this issue May 9, 2023 · 1 comment
Assignees
Labels
api Issues related to the API used by Mod Devs ux Issues focused on user experience improvements

Comments

@mkahvi
Copy link

mkahvi commented May 9, 2023

User Experience

For example player cursor position is not critical data, it shouldn't be transmitted as if it had to reach destination no matter what.

Ref: https://socket.io/docs/v3/emitting-events/#volatile-events

It's not quite as good as proper UDP, but it potentially removes some pointless network traffic.

I unfortunately didn't spot any other message types that would benefit from this, but even using it for cursor can help people with flaky connection not having to constantly buffer more and more.

@aaclayton aaclayton self-assigned this May 9, 2023
@aaclayton
Copy link
Contributor

Good suggestion and an easy improvement.

@aaclayton aaclayton added ux Issues focused on user experience improvements api Issues related to the API used by Mod Devs labels May 9, 2023
@aaclayton aaclayton added this to the Version 11 - Testing 2 milestone May 9, 2023
@aaclayton aaclayton changed the title Use volatile socket messages for non-critical data (e.g. player cursor position) Emit user activity data using a volatile socket event to prevent unnecessary buffering of non-critical data. May 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Issues related to the API used by Mod Devs ux Issues focused on user experience improvements
Projects
Status: Done
Development

No branches or pull requests

2 participants