Skip to content

Missing WebSocketServerTransport? #142

Closed

Description

@calclavia

Is your feature request related to a problem? Please describe.
I noticed there's a WebSocketClientTransport in this SDK, but no corresponding WebSocketServerTransport. Is that planned to be added (should I make a PR and contribute it?)

Activity

  1. added
    enhancementRequest for a new feature that's not currently supported
    on Jan 27, 2025
  2. jspahrsummers commented on Feb 4, 2025

    @jspahrsummers
    Member

    tbh we should probably remove the WS transport that's there. It's useful to demonstrate that others are possible (e.g., in isolated use cases), but we don't want a proliferation of transports, because it explodes the number of combinations that servers and clients have to support for interoperability.

  3. added
    ready for workEnough information for someone to start working on
    P2Moderate issues affecting some users, edge cases, potentially valuable feature
    on Oct 24, 2025
  4. felixweinberger commented on Oct 24, 2025

    @felixweinberger
    Contributor

    Would be a good cleanup to remove the client websocket - maybe replace with an inMemory transport instead kinda like we have in Python? To make it more obvious it's an example and not intended for reuse.

  5. calclavia commented on Oct 25, 2025

    @calclavia
    MemberAuthor

    Agree - should remove now that the community have moved to streamable http.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Moderate issues affecting some users, edge cases, potentially valuable featureenhancementRequest for a new feature that's not currently supportedready for workEnough information for someone to start working on

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions