Open wss-alubic opened 1 month ago
Not yet, is this a critical issue for you? I thought polling was enough in most cases.
We've got a Blazor WASM app that currently calls our .NET API to resolve feature flags. We decided not to add the FeatBit .NET Server SDK to it because the Client SDK was coming.
Our plans are to hold off until the Client SDK can support websockets. We're concerned that polling across all clients would cause too much unnecessary network traffic.
I wouldn't say it's critical because our current solution works just fine.
Got it, make sense for me. What do you think? @cosmic-flood
Are there any plans to port the WebSocketDataSynchronizer to the Client SDK?