I have a question around the .NET SDK and the implementation of websockets:
Notifications are using WebSocketSharp, and this library is a pre-release, not updated since 2016. Can we confirm this customer the use of this Websocket implementation is going to be safe and estable from Product perspective? What customer doesnt want is to discover this library had a bug or something causing unexpected behaviors.
Also, I have a question related with limits itself for these notifications:
In the limits resource (https://developer.genesys.cloud/organization/organization/limits) it says app.user.channels.max is "The maxium number of active channels per OAuth client per user". So if we are using an OAuth client of type Code Auth, and we have 600 users, each user is going to have 20 channels, so at the end, 1200 channels for this OAuth client?
I've never met a company that will guarantee the safety and stability of a 3rd party component they're using. It's been in use ~8 years so far and that's about the best warranty you're going to get. The built in websocket functionality isn't required, it's a nice-to-have and anyone with concerns about it's safety and stability can opt to not use it or use a 3rd party websocket of their choice.
Thanks for responding. I agree with you. We used this library when the .NET SDK was first built and the developer of the package never went beyond this. We will remediate a bug or a critical vulnerability scan if we encounter an issue with a third-party library, but otherwise, we are not going to do anything further with the library.
Thanks,
John Carnell
Director, Developer Engagement