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

fix(engineio/socket): atomically adjacent packet requirement for binary payloads #287

Merged
merged 5 commits into from
Mar 20, 2024

Conversation

Totodore
Copy link
Owner

Motivation

Solution

Change the engine.io socket internal channel so that it can take multiple packets at once. It is backed by smallvec which allows to put packets on the stack for small sizes before moving to the heap. This will avoid slowdowns where there is only one packet sent (most of the time).

@Totodore Totodore added bug Something isn't working engineio-v3 It is only about the version 3 of the engine.io protocol engineio-v4 It is only about the version 4 of the engine.io protocol labels Mar 19, 2024
@Totodore Totodore self-assigned this Mar 19, 2024
@Totodore Totodore merged commit fb24479 into main Mar 20, 2024
12 checks passed
@Totodore Totodore deleted the fix-adjacent-bin-payload branch March 20, 2024 19:30
Totodore added a commit that referenced this pull request Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working engineio-v3 It is only about the version 3 of the engine.io protocol engineio-v4 It is only about the version 4 of the engine.io protocol
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Inconsistent binary packet ordering
1 participant