Suggesting that somethig like /analysis would list all of the UUIDs on file.
In general, I am pushing for using the API's persistent store more instead of relying on the client side to retain information.
Problems with the client-side keeping request information and status:
requests can be issued independently by several clients using the same API key,
clients can crash or lose their persistent store
client have to be less light weight if they have to maintain a persistent store and handle merging results from parallel jobs
This is related to issue #18 .
In sum, making more use of mythril-api's persistent storage, adds value to mythril-api.
Suggesting that somethig like /analysis would list all of the UUIDs on file.
In general, I am pushing for using the API's persistent store more instead of relying on the client side to retain information.
Problems with the client-side keeping request information and status:
requests can be issued independently by several clients using the same API key, clients can crash or lose their persistent store client have to be less light weight if they have to maintain a persistent store and handle merging results from parallel jobs This is related to issue #18 . In sum, making more use of mythril-api's persistent storage, adds value to mythril-api.