This release introduce the new volatile operator. When set, the emitted event may be dropped if the client is not ready to receive it (e.g. the connection is buffering or not connected). This is useful for events that are not critical, such as position updates in a game.
Changelogs
engineioxide-core 0.2.2
- refactor: move polling payload encoder/decoder to
core. - chore(deps): bump cmov from 0.5.3 to 0.5.4
engineioxide 0.17.6
- feat: add
emit_{binary,many}_volatilemethods toSocketto emit volatile packets.
socketioxide-core 0.18.2
- feat: add new
Volatilebroadcast flag
socketioxide 0.18.5
- feat: add
volatile()flags to emit without guaranteeing delivery, this allows to avoid filling internal
buffers and improve performance #602. - chore(deps): bump cmov from 0.5.3 to 0.5.4
What's Changed
- chore(deps): bump actions/cache from 5 to 6 by @dependabot[bot] in #750
- chore(deps): bump actions/checkout from 6 to 7 by @dependabot[bot] in #749
- chore(deps): bump cmov from 0.5.3 to 0.5.4 by @dependabot[bot] in #751
- chore(deps): bump cmov from 0.5.3 to 0.5.4 in /examples by @dependabot[bot] in #752
- refactor(engineio): move shareable constructs with future client to core by @Totodore in #555
- feat: volatile emits by @Totodore && @LiamCarPer in #753
New Contributors
- @LiamCarPer made their first contribution in #753
Full Changelog: socketioxide-v0.18.4...socketioxide-v0.18.5