You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?)
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.
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.
Activity
jspahrsummers commentedon Feb 4, 2025
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.
felixweinberger commentedon Oct 24, 2025
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.
calclavia commentedon Oct 25, 2025
Agree - should remove now that the community have moved to streamable http.