Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AgencyRPCs and History should offer clear methods #3

Open
faultyserver opened this issue Aug 13, 2016 · 0 comments
Open

AgencyRPCs and History should offer clear methods #3

faultyserver opened this issue Aug 13, 2016 · 0 comments

Comments

@faultyserver
Copy link
Member

When updates are pushed to shark, particularly ones that change data structures of events, it can take a long time (potentially forever) for those changes to propagate and update all existing data objects.

To remedy this, there should be RPCs that clear the caches these components hold, removing all stale data that may have been rendered structurally-incorrect by an update.

I would suggest something like agency.__clear for AgencyRPCSession, with the dunderscore indicating that this is not a normal rpc, and meta.__clear_history for HistorySession.

These procedures could additionally take arguments to give more granular control over what gets cleared by a single call.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant