Yasser Fadl
Yasser Fadl
I think this depends on us implementing a close event on the protocol both ways which can inform clients to reconnect (will force it to reroute to another deepsteam). The...
I agree this is a good improvement to provide a graceful stop, we will prioritize accordingly.
This is the next feature we want to add into deepstream post presence, so will be sometime by end of year.
We are looking to add a concept of version number `-1`. What this will do is bypass the version conflict in record transition, load the last object, apply the patch...
If you could add the `-1` version that would be awesome. > I can do some research on what Redis, mongo and others support for list operations and propose and...
Keeping this issue open as lists is the killer feature deepstream needs. It’s also not the easiest to implement and hence will most likely not come to be. Here’s to...
This will fall under the 4.5 release with the admin API (basically the ability to refresh permissions and kickout users for now)
Linking to #787
Unfortunately the admin API was pushed out of scope to client projects pivoting on usecase. There is some work by the community potentially on a kick out user feature. Using...
Easiest way to deal with this is to do rolling. If the number is 2147483647 then go back to zero. Will end up having all the clients needing to just...