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
{{ message }}
This repository has been archived by the owner on May 14, 2020. It is now read-only.
Is it or will it be possible to push only the relevant records (filtered records) as required by the client, i.e. watch for changes on filtered data.
#15
Open
abhinavzspace opened this issue
Nov 21, 2016
· 1 comment
Suppose I have a filter for collection/collection_id_1?status=true. So through this I am getting just those records with status = true inside collection_id_1 collection. Now when one of the records with status = false changes on some other client, then I don’t want to inform this particular client who is working on records with status = true.
In short, if a client is working with records 1, 2 and 3, then I would never want to send notifications to it for records 4, 5 and 6.
Is this way already possible or any workaround that exists? Because this feature will really make it usable for a lot of applications. Even if its not possible to do this now, is there any future hope for its implementation?
We are thinking of porting an application in firebase to kinto but currently only this requirement is stopping us.
The text was updated successfully, but these errors were encountered:
Suppose I have a filter for
collection/collection_id_1?status=true
. So through this I am getting just those records withstatus = true
inside collection_id_1 collection. Now when one of the records withstatus = false
changes on some other client, then I don’t want to inform this particular client who is working on records withstatus = true
.In short, if a client is working with records 1, 2 and 3, then I would never want to send notifications to it for records 4, 5 and 6.
Is this way already possible or any workaround that exists? Because this feature will really make it usable for a lot of applications. Even if its not possible to do this now, is there any future hope for its implementation?
We are thinking of porting an application in firebase to kinto but currently only this requirement is stopping us.
The text was updated successfully, but these errors were encountered: