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 was archived by the owner on Oct 19, 2018. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 19, 2018. It is now read-only.
Don't send an updates to clients if the filtered changes are empty #107
when using auth_logic (for example) when a logged user makes ANY request to the server, this updates the user model, which causes data to be pushed to the client
which causes the client to update its scopes
which is another request
and so on...
so the solution should be don't sync those attributes to the client
so hyper-mesh filters out those attributes, but the problem is even if you have an empty set of attributes, the update is still being sent, causing the scope resync...
when using auth_logic (for example) when a logged user makes ANY request to the server, this updates the user model, which causes data to be pushed to the client
which causes the client to update its scopes
which is another request
and so on...
so the solution should be don't sync those attributes to the client
so hyper-mesh filters out those attributes, but the problem is even if you have an empty set of attributes, the update is still being sent, causing the scope resync...