[Renamed subject to match the other thread]
> From what I can see sendmail caches open connections to hosts,
> keeping them open for a short time so that any subsequent
> messages to the same host can be delivered on the existing
> open connection.
> From what I can see this would require us to cache "Transport"s
> in RemoteDelivery, test with Transport.isConnected() and only
> connect if the answer is no. Unless JavaMail is already only
> creating single Transports for each URLName, in which case the
> conditional connect/close would help.
>From what I am reading on their mailing list (I haven't looked at the code,
yet), JavaMail is inefficient in the SMTP transport. They don't even use a
threadpool. Everything is done new and fresh for each connection. Keeps
resource use low for typical clients, but not efficient for high-speed
delivery.
> I can see that it would also help if we could get messages
> by hostname, when we would then be able to guarentee useing
> a single session for all mail to a single host, but this
> would require, as you say, overhaul of the spool interface.
Yup.
> On the other hand if we could somehow make Mail a
> ConnectionListener on the relevant Transport then we
> could use an event driven remote delivery which would
> work, perhaps, by adding mail to the transport as a
> listener
That would require keeping the mail instances live in memory.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
