RE: Saving session information
Hmm. Thats the James 3 version of org.apache.mailet.Mail, not the current version. Guess its coming but not here yet. It is the MailetAPI v3 d.
Saving session information
Hi, I have several mailets that are used in the processing of mail messages. A couple of them end up querying a database for the same information; in this case, some properties related to the sender and/or recipients. I was thinking it would be nice if this information could be cached someplace (like in the Mail object?) and pulled out by the each mailet as needed. Obviously the lifetime of the cached information is pretty short; once the message is stored/forwarded it's gone but it still seems like it could be useful. Does this functionality exist? Does it make sense or is there a better way to get this functionality? Thanks. Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Saving session information
I was thinking it would be nice if [meta-data about a message] could be cached someplace (like in the Mail object?) and pulled out by the each mailet as needed. Mail attributes are coming. They were planned for James v3, but it looks like they will make it into James v2.2. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Saving session information
Look at org.apache.mailet.Mail getAttribute() setAttribute(). Seems to be what you are looking for. Never tried it though. -- Steve -Original Message- From: Jim Janson [mailto:[EMAIL PROTECTED] Sent: 25 June 2003 21:52 To: James Users List Subject: Saving session information Hi, I have several mailets that are used in the processing of mail messages. A couple of them end up querying a database for the same information; in this case, some properties related to the sender and/or recipients. I was thinking it would be nice if this information could be cached someplace (like in the Mail object?) and pulled out by the each mailet as needed. Obviously the lifetime of the cached information is pretty short; once the message is stored/forwarded it's gone but it still seems like it could be useful. Does this functionality exist? Does it make sense or is there a better way to get this functionality? Thanks. Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]