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 Apr 17, 2023. It is now read-only.
Problem is that this will require users to know their datasets all the time and init them directly in the server. I think it will be nice to have global sync frequency setup on the server so users will still have configuration to tweak for all the requests. Alternative will be to support passing syncFrequency in the client.
By default now everything will be done even 10 seconds which may impact performance.
The text was updated successfully, but these errors were encountered:
👍 I think having a global overridable default for new datasets would be helpful.
I think a separate frequency per client might be a much bigger change, but I think there are scenarios where this level of fine-grain could help with valuable tweaks.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current sync api requires us to register dataset on the server to change sync frequency.
Problem is that this will require users to know their datasets all the time and init them directly in the server. I think it will be nice to have global sync frequency setup on the server so users will still have configuration to tweak for all the requests. Alternative will be to support passing syncFrequency in the client.
By default now everything will be done even 10 seconds which may impact performance.
The text was updated successfully, but these errors were encountered: