mendicant-university/newman — Issue #5: other response models - broadcast, no response, delayed response etc.
Author: ericgj
Created: 2012-02-04 16:18:17+00:00
State: open

Right now the server model is single-request, single-response. It's easy to think of other use-cases that don't fit this model: for instance

1. broadcast 'mail-merge' emails,
2. email that just sends a command and doesn't need any response,
3. response emails get queued up or combined for later delivery, e.g. 'digest' emails might work this way

None of these seem high priority for us, in fact I'd be happy never to build a platform for spam (#1) :)

But something to consider at some point whether the *app* should have more control over the response flow, rather than the *server*.