{"action":"opened","issue":{"url":"https://api.github.com/repos/propershark/crossbar-router/issues/3","repository_url":"https://api.github.com/repos/propershark/crossbar-router","labels_url":"https://api.github.com/repos/propershark/crossbar-router/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/propershark/crossbar-router/issues/3/comments","events_url":"https://api.github.com/repos/propershark/crossbar-router/issues/3/events","html_url":"https://github.com/propershark/crossbar-router/issues/3","id":171020595,"number":3,"title":"AgencyRPCs and History should offer `clear` methods","user":{"login":"faultyserver","id":783733,"avatar_url":"https://avatars.githubusercontent.com/u/783733?v=3","gravatar_id":"","url":"https://api.github.com/users/faultyserver","html_url":"https://github.com/faultyserver","followers_url":"https://api.github.com/users/faultyserver/followers","following_url":"https://api.github.com/users/faultyserver/following{/other_user}","gists_url":"https://api.github.com/users/faultyserver/gists{/gist_id}","starred_url":"https://api.github.com/users/faultyserver/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/faultyserver/subscriptions","organizations_url":"https://api.github.com/users/faultyserver/orgs","repos_url":"https://api.github.com/users/faultyserver/repos","events_url":"https://api.github.com/users/faultyserver/events{/privacy}","received_events_url":"https://api.github.com/users/faultyserver/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-13T18:12:50Z","updated_at":"2016-08-13T18:12:50Z","closed_at":null,"body":"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.\r\n\r\nTo 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.\r\n\r\nI 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`.\r\n\r\nThese procedures could additionally take arguments to give more granular control over what gets cleared by a single call."}}
{"actor":{"display_login":"faultyserver"}}