Re: [Zope] oddity in MailHost queue processor thread

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Maric Michaud wrote: Tres Seaver a écrit : I was surprised by the behavior of asynchronous mailing in zope 2.11.3 MailHost product. It creates a thread by instance of MailHost by the mean of using self.absolute_url(1) as key for the

[Zope] oddity in MailHost queue processor thread

Hi all, I was surprised by the behavior of asynchronous mailing in zope 2.11.3 MailHost product. It creates a thread by instance of MailHost by the mean of using self.absolute_url(1) as key for the queue_threads dictionnary. It seems obviously wrong, IMO, if several instances share the same

Re: [Zope] oddity in MailHost queue processor thread

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Maric Michaud wrote: Hi all, I was surprised by the behavior of asynchronous mailing in zope 2.11.3 MailHost product. It creates a thread by instance of MailHost by the mean of using self.absolute_url(1) as key for the queue_threads

Re: [Zope] oddity in MailHost queue processor thread

Tres Seaver a écrit : I was surprised by the behavior of asynchronous mailing in zope 2.11.3 MailHost product. It creates a thread by instance of MailHost by the mean of using self.absolute_url(1) as key for the queue_threads dictionnary. It seems obviously wrong, IMO, if several