[z3-five] MailHosts as utilities

[Philipp von Weitershausen]

Chris Withers wrote:
> Rocky Burt wrote:
>> Well, whatever interface we end up using the need I see is as follows:
>>
>>   1) use existing zope3 mail interface (or create new one like
>> IMailHost)
> 
> I wonder what the existing zope3 mail interfaces looks like? I'd be 
> pleasantly surprised if MailHost already has the required methods :-)

Gee, Chris. If only you could see the source code of Zope 3 or there was 
a tool that would let you inspect every interface in Zope 3 or there was 
a book that covered this... Shame, shame...

>>   2) make sure global utility exists for this interface
> 
> Really? I'd prefer no global utility were available by default - 
> possible spam sources should not exist by default...

Right, that doesn't seem like a necessity. It's certainly not the case 
in Zope 3. Sending emails is highly deployment specific.

>>   3) make persistent version of utility that can be registered locally
>> and stores it's settings internally
> 
> I'd like to see existing MailHost-ish things fulfill this roll.

Sure, though it'd be nice to have the same interface for both global 
utilities that can be defined in Zope 3 and local ones. Then code 
wanting to send emails wouldn't have to bother which one it wnats.


-- 
http://worldcookery.com -- Professional Zope documentation and training
2nd edition of Web Component Development with Zope 3 is now shipping!