Skip to content

In_Memory_Data_Store.md

Latest commit

 

History

History
45 lines (24 loc) · 2.45 KB

In_Memory_Data_Store.md

File metadata and controls

45 lines (24 loc) · 2.45 KB
graph LR
    Global_State_Manager["Global State Manager"]
    Data_Instance_Controller_DtaleInstance_["Data Instance Controller (DtaleInstance)"]
    View_Layer_Flask_Views_["View Layer (Flask Views)"]
    Data_Instance_Controller_DtaleInstance_ -- "Registers with" --> Global_State_Manager
    View_Layer_Flask_Views_ -- "Fetches instance from" --> Global_State_Manager
Loading

CodeBoardingDemoContact

Details

One paragraph explaining the functionality which is represented by this graph. What the main flow is and what is its purpose.

Global State Manager

This component implements the singleton pattern to act as a central, in-memory registry for all active data instances. It is responsible for the entire lifecycle of the data, including storage, retrieval, and cleanup. Its global nature ensures that any part of the application can access any dataset if it has the correct identifier.

Related Classes/Methods:

  • dtale.global_state

Data Instance Controller (DtaleInstance)

This class acts as a wrapper or controller for a single pandas DataFrame. Each DtaleInstance object encapsulates one dataset and its associated metadata. Upon instantiation, it registers itself with the Global State Manager to make the dataset available to the rest of the application. It is the primary object that other components interact with to perform data-specific operations.

Related Classes/Methods:

View Layer (Flask Views)

The View Layer consists of Flask view functions that serve as the HTTP endpoints for the frontend. These functions handle incoming web requests, which typically include a data instance ID. They use this ID to query the Global State Manager, retrieve the appropriate DtaleInstance, and then perform actions or serve data based on the request.

Related Classes/Methods:

  • dtale.views

FAQ