Skip to content

Tighten and document optional socket dependency features #1

Description

@bnomei

Context

Socket support stays, but its dependency cost should be tightened where possible. If upstream prevents unifying duplicate reqwest/TLS stacks, document that cost on the socket feature.

Tasks

  • Inspect rust_socketio and rust_engineio feature flags and newer versions.
  • Disable unnecessary default features where supported.
  • Document unavoidable duplicate HTTP/TLS dependencies if they remain.

Acceptance criteria

  • Socket feature dependencies are as narrow as practical.
  • Unavoidable dependency duplication is documented.
  • Socket support remains available.

Notes

  • Generated from the project improvement research pass.
  • Keep implementation discussion repository-relative; do not include local machine paths or private setup details.

Activity

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions