Tom Hacohen a54afd5210 Optimize stoken-using functions to only account for current revisions. ... No need to account for revisions that are not current when calculating stokens because those, by definition, are not the latest ones, and therefore won't have the most recent stokens. This becomes a problem when collections have many associated revisions.		2023-08-15 20:21:23 -04:00
..
migrations	fix: move django_etebase module from toplevel to under etebase_server	2022-05-09 17:41:16 +02:00
token_auth	fix: move django_etebase module from toplevel to under etebase_server	2022-05-09 17:41:16 +02:00
__init__.py	fix: move django_etebase module from toplevel to under etebase_server	2022-05-09 17:41:16 +02:00
app_settings_inner.py	fix: move django_etebase module from toplevel to under etebase_server	2022-05-09 17:41:16 +02:00
apps.py	fix: move django_etebase module from toplevel to under etebase_server	2022-05-09 17:41:16 +02:00
models.py	Optimize stoken-using functions to only account for current revisions.	2023-08-15 20:21:23 -04:00
signals.py	fix: move django_etebase module from toplevel to under etebase_server	2022-05-09 17:41:16 +02:00
utils.py	fix: move django_etebase module from toplevel to under etebase_server	2022-05-09 17:41:16 +02:00