send emails & generate reports asynchronously

[kelseyq]

Looks like there are a lot of options for doing this in Python

[willingc]

Might be good to start with the Django cookicutter's suggestion for AnyMail since it avoids lock in for a single mail provider.

[kelseyq]

I think that might be a different issue--this one refers to running the code that generates reports & sends emails asynchronously, so the webapp can respond while that's happening.

[willingc]

Let me see if I've got the use case:

• webapp is running
• when no requests are coming in to the webapp, the webapp begins generating reports and sending emails
• if a request comes in to the webapp, the webapp triggers the report generation/email to wait until the requests have been serviced.
• when the requests/responses are complete, the webapp may unblock the report generation/email and continue reporting and emailing.

[kelseyq]

These calls: https://github.com/SexualHealthInnovations/callisto-core/blob/master/callisto/delivery/views.py#L47 https://github.com/SexualHealthInnovations/callisto-core/blob/master/callisto/delivery/views.py#L64 https://github.com/SexualHealthInnovations/callisto-core/blob/master/callisto/delivery/views.py#L123 potentially take a long time and could be handled in a coroutine/Celery/Twisted/other form of asynchronous process, allowing the site to return a response to the user while that's happening. Error handling would need to be considered. This is an idea for a future improvement and not a high-priority issue.

[kelseyq]

@willingc any ideas on tagging issues to indicate priority or scope?

[willingc]

@kelseyq Perhaps create milestones for next release, release + 1, wish list. Or labels with one color to signify priority [pri: critical], [pri: next release], [pri: wishlist]. Overall, keep it simple ;-)

[willingc]

Oh and you already are doing a great job tagging issues. 🎉