FinnStutzenstein 23842fd496 Synchronize autoupdate code in the client ... If autoupdates are too fast, the first one may not be fully executed. Especially when the maxChangeId is not yet updated, the second Autoupdate will trigger a refresh, because for the client it "lay in the future". This can be prevented by synchronizing the autoupdate-handling code with a mutex.		2020-05-22 15:23:53 +02:00
..
agenda	Add tags for agenda items	2020-05-14 15:07:59 +02:00
assignments	Adds migration to remove deprecated slides	2020-05-19 12:55:47 +02:00
core	Fix unnecessary and unfunctional lock for production usage with gunicorn	2020-05-06 16:57:50 +02:00
mediafiles	Last changes and cleanup some todos	2020-03-17 07:24:50 +01:00
motions	Updated translations	2020-05-14 19:52:18 +02:00
poll	added config for default poll type	2020-05-14 07:38:14 +02:00
saml	saml	2019-10-21 13:34:01 +02:00
topics	adds more permissive html validation	2020-04-16 10:26:48 +02:00
users	Updated translations	2020-05-14 19:52:18 +02:00
utils	Synchronize autoupdate code in the client	2020-05-22 15:23:53 +02:00
__init__.py	Prepare new 3.2 release	2020-04-16 13:41:56 +02:00
__main__.py	saml	2019-10-21 13:34:01 +02:00
asgi.py	saml	2019-10-21 13:34:01 +02:00
global_settings.py	Fixes python3.7 tests	2019-10-29 15:05:52 +01:00
routing.py	Closing websocket connections to unknown urls	2019-10-15 10:54:31 +02:00
urls_apps.py	saml	2019-10-21 13:34:01 +02:00
urls.py	[WIP] External postgres as mediafile store	2020-02-17 14:38:32 +01:00