> > session), but in any case, it seems to me that a Source can keep a > > cache of open Connections itself if necessary - it doesn't > really have > > to be stored in the Session. > > You can do this (connection pooling) in MailSourceFactory, or, if such > connection pool can be reused somewhere else, it could be a separate > connection pool component (a-la datasource).
Cheers Vadim It also strikes me that the user's credentials could be stored in a session using an Action (this is what Justin was suggesting, I see now), so that the SessionTransformer could insert these data into "mail:" URLs, and XInclude could resolve these resulting URLs using the MailSource. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
