Make IMIP flow asynchronous ? #147
Description
Context:
- Some calendar updates (recursive, with numerous attendees) are fucking slow CF 504 Accepting a recurring event with many attendes #128
- It seems link with IMIP CF Optimize cascading notifications for events with many attendees #142
While we can find relevant heuristics not to process IMIP for attendee partstate changes (for other attendees), it is still true that updating an attendee with numerous attendants will remain painful!
Proposal:
While we might have addressed a edge case, we still remain another one: we clearly see that IMIP processing can be long and heavy. Another approach is actually architectural: that a good hint that we should make IMIP processing asynchronous. We could EG serialize the IMIP payload and publish it in a queue, return, and have the side service do a HTTP call to resume asynchronously the IMIP process.
We won't have made the process faster but this slowness will be fully hidden to the end user.