On Dec 21, 2004, at 1:42 PM, Kevin A. Burton wrote:
Kevin A. Burton wrote:
FYI... I was thinking on the way home that one could register their OWN transport which was threaded. The only problem is that the Transport class assumes its synchronous.Transport.send() usually blocks.
It seems to make sense to add a param to SMTPAppender to simply accept messages for delivery and them hand them off to a dedicated thread so that hte caller can return from log.info()...
Thoughts?
Though you could forward all these methods to the threaded class.
Have you tried encapsulating the SMTPAppender in an AsyncAppender? Were there problems with that approach?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
