11. Refactoring galley to support large conversations
To be able to suppport large conversations galley needs refactoring. This section in the developer docs is meant to contain useful references for this endeavor.
11.1. Call hierarchy
See large-conversations.yaml for call hierarchy of functions that load the full member list into memory.
11.2. Galley Endpoints
These are all the endpoints in galley with response types that contain the full member list of conversations.
EventData might contain a
Conversation object, but it’s not clear from API type alone if it contains one)
MLSMessageSendingStatuswhich contains list of
Event, as well a list of unreachable users.
mls-messagereturns list of
MessagingAPI (Proetus) is not listed here, assuming that Proteus conversations won’t support large conversations.