Use a database table to hold the users that should have full presence sent to...
Use a database table to hold the users that should have full presence sent to them, instead of something in-memory (#9823)
Showing
- changelog.d/9823.misc 1 addition, 0 deletionschangelog.d/9823.misc
- docs/presence_router_module.md 5 additions, 1 deletiondocs/presence_router_module.md
- synapse/handlers/presence.py 110 additions, 26 deletionssynapse/handlers/presence.py
- synapse/module_api/__init__.py 30 additions, 33 deletionssynapse/module_api/__init__.py
- synapse/replication/http/presence.py 9 additions, 2 deletionssynapse/replication/http/presence.py
- synapse/rest/admin/server_notice_servlet.py 5 additions, 3 deletionssynapse/rest/admin/server_notice_servlet.py
- synapse/storage/databases/main/presence.py 57 additions, 1 deletionsynapse/storage/databases/main/presence.py
- synapse/storage/schema/main/delta/59/13users_to_send_full_presence_to.sql 34 additions, 0 deletions...schema/main/delta/59/13users_to_send_full_presence_to.sql
- tests/events/test_presence_router.py 11 additions, 4 deletionstests/events/test_presence_router.py
- tests/module_api/test_api.py 216 additions, 87 deletionstests/module_api/test_api.py
- tests/replication/test_sharded_event_persister.py 1 addition, 1 deletiontests/replication/test_sharded_event_persister.py
Loading
Please register or sign in to comment