tag:blogger.com,1999:blog-19026079.post6760291889322866987..comments2007-12-27T10:21:42.062+01:00Hanno Schlichtinghttp://www.blogger.com/profile/02880767944793425548hannosch@gmail.comBlogger2125tag:blogger.com,1999:blog-19026079.post-57353490284990230512007-12-27T10:21:00.000+01:002007-12-27T10:21:00.000+01:00At any rate, it's a leap forward in terms of code clarity that there's now only a single implementation to focus on. Relevant especially around Christmas, Plone needs to lose weight.malthehttp://www.blogger.com/profile/06350993952511336935noreply@blogger.comtag:blogger.com,1999:blog-19026079.post-67308940905333438292007-12-27T02:20:00.000+01:002007-12-27T02:20:00.000+01:00On the flip side, IIRC, the asynchronous Zope 3 mailhost code has its own problems. You need to configure it to run on only one of your ZEO clients, as running it in more than one is silly, but that means changing your config per ZEO host in a place not in the config file. It would be better if it the sending was done by a dedicated process, releasing any client from the responsibility. IIRC, it's also not very smart about dealing with send failures.chrismhttp://www.blogger.com/profile/10365119734346418304noreply@blogger.com