Was WatsonWsClient excluded from the migration?

[enricobenedos]

Hi @jchristn,
I'm using the recently archived WatsonWebsocket Nuget package. I noticed that that the client doesn’t seem to have been ported.

It was a very useful accelerator for WebSocket client projects. Do you think it might be introduced in the future, or is there no plan to port it?

[jchristn]

Hi @enricobenedos thanks for your note - this was an oversight on my part; I should have included it. I'll work on it now. Thanks for the push.

[jchristn]

Hi @enricobenedos just published a new NuGet package Watson.Clients - source is here: https://github.com/dotnet/WatsonWebserver/tree/main/src/Watson.Clients

NuGet here: https://www.nuget.org/packages/Watson.Clients/7.0.14

Thanks for the nudge, and re-open if any issues!

[enricobenedos]

Hi @jchristn,

Thank you for the new client implementation.

I don’t want to bother you, but I may be missing something about this migration. I really liked the original Watson client and server implementation because it avoided having to repeatedly rewrite the same codebase on top of Microsoft ClientWebSocket, and it greatly simplified the work for low-code implementations.

While trying to migrate to the new foundation implementations, I noticed that the client and server implementations appear to have changed significantly, and this seems to break compatibility with the previous approach.

Could you clarify the intended migration path, or whether there is a recommended way to preserve the simpler client/server usage pattern from the original Watson implementation?

Thank you 😊

[jchristn]

Hi @enricobenedos no bother at all, do you have specific examples in mind? The API surface for the server-side HTTP should be almost entirely consistent. The server-side websockets implementation has fundamentally changed, as Watson Websocket used the underlying http.sys implementation, and wasn't extensible to support a converted HTTP/websockets application. The client implementation for websockets was sorely missing until you pointed it out, but the implementation in Watson.Clients should be largely consistent.

[jchristn]

Also added more clarity in the Watson.Clients README: https://github.com/dotnet/WatsonWebserver/tree/main/src/Watson.Clients

[enricobenedos]

Thank you @jchristn,
maybe I was only trying to say that it isn't a simple packages migration with some little code changes.
I've both a server and client implementation that cannot be simply migrated to this new implementation. An example are missing events, probably who were using the old library cannot simply adopt this one.

Anyway I'm really happy your package have been accepted by .NET foundation 😉

[jchristn]

Thank you @enricobenedos - if there are missing events please let me know and I'll do what I can to remedy that!