Currently, the library only supports in memory storage for the message sessions. Ideally, we would also have a way to persist this to a database and load it dynamically.
A possible flow for doing this would be:
[ ] Create a way to serialize / deserialize a store object.
[ ] Use an ORM such as peweee (+maybe pydantic for model definitions).
[ ] Hook that to the in-mem storage
Once we have a working impl, we can see where it is best to use it (e.g. should we discard the inmem storage altogether or maybe just fetch from db / save from db on certain lifecycle events of mitmproxy -- proxy started / stopped).
Currently, the library only supports in memory storage for the message sessions. Ideally, we would also have a way to persist this to a database and load it dynamically.
A possible flow for doing this would be:
Once we have a working impl, we can see where it is best to use it (e.g. should we discard the inmem storage altogether or maybe just fetch from db / save from db on certain lifecycle events of mitmproxy -- proxy started / stopped).