Skip to content
This repository was archived by the owner on Jul 16, 2020. It is now read-only.

Operator Cache

Jump to bottom
Aaron Graubert edited this page May 22, 2019 · 3 revisions

Operator Cache

Note: Since Lapdog version 0.16.0 the Operator Cache has been migrated into Dalmatian. The wiki page will stay here for now, but it will accurately represent the current state of the cache

Every Workspace Manager (dalmatian.WorkspaceManager) maintains a cache layer between local resources and FireCloud. This cache, the "operator" is enabled for most calls to FireCloud, such as getting and updating entity metadata, methods, and configurations.

Offline Mode

By default, the operator runs in "Online Mode", where all requested data is fetched live from FireCloud and all local changes to data are pushed out to FireCloud. However, an operator may switch to "Offline Mode" in any of the following conditions:

  • The FireCloud API returns an unhandled error condition
  • The FireCloud API takes too long to return any data:
    • 5 seconds if the requested data is already cached, but may be out of date
    • 30 seconds otherwise
  • The user manually switches to offline mode with dalmatian.WorkspaceManager.go_offline()

To switch back into online mode, you must call dalmatian.WorkspaceManager.sync(). When switching back to online mode, the workspace will replay any local changes made to the workspace back to FireCloud

Clone this wiki locally