I think what people have in mind (correct me if I am wrong) is
something that will accept messages (for posting to the mailhost at
some time in the future) and then immediately return. I guess it would spawn
another process/thread to do the posting asynchronously.
The problem, as I see it is how to handle an error with the
posting. The user who submitted the mail is now long gone so it must
be left to an administrator to pick up the pieces.
Perhaps the posting routine could accept a user (developer) provided
exception handler that gets called if a posting fails.
It maybe better to just hand this off to a completely separate program
rather than try to handle it within a zope thread.
[EMAIL PROTECTED] writes:
> Out of curiosity, what exactly is a non-blocking MailHost?
> On Mon, Sep 04, 2000 at 09:31:15AM +0100, Chris Withers wrote:
> > What we really want is a non-blocking MailHost.
> > Anyone know how or want to write one?
Zope maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -