Right now the demo is using class variables to hold the type and list across requests. It would be better if, for each user, their data (different for quick/regular) was stored in a Redis hashtable. That way, results would only have to be loaded once (unless the user chose to refresh) and the issues with class variables wouldn't matter anymore.
Right now the demo is using class variables to hold the type and list across requests. It would be better if, for each user, their data (different for quick/regular) was stored in a Redis hashtable. That way, results would only have to be loaded once (unless the user chose to refresh) and the issues with class variables wouldn't matter anymore.