List view
- No due date
This should rely on the ability to run filters in the Yokan database.
No due date- No due date
- No due date
There are three difficulties here: 1. These objects should be callable potentially concurrently (if a thread pool is provided). Since Python has a GIL, we need to wrap them into a ULT and force this ULT to run on the ES that initialized the Python interpreter. 2. These objects should be serialized into the master database and loadable from there. This could be done using the [dill](https://github.com/uqfoundation/dill) library, which handles serializing Python functions/callables. 3. These objects should be usable from a C++ program, which means we need to check if an interpreter has been initialized and, if not, initialize it ourselves.
No due dateCurrently the data selector and the data broker are provided in C++ by passing a lambda directly from the user code. This milestone would add the possibility to load such a selector and broker from a shared library, allowing something like the following: ``` auto my_selector = mofka::DataSelector::FromDynamicLibrary("myselector:/path/to/the/library.so"); auto my_broker = mofka::DataBroker::FromDynamicLibrary("mybroker:/path/to/the/library.so"); ``` The symbols looked up should be registered in a factory. In Python, we will need a think about a way to handle the returned `mofka::Data` object as a `memoryview`.
No due date