My idea was to always do an outgoing.accept(0) and set the MailslastUpdatedto currentTimeMillis+the next delay for that mail-
MailImpl.writeObject always does a lastUpdated=new Date() prior to the actual storing of the object, which effectly prevents me from dating the mail into the future.
What is the rationale behind this?
lastUpdated is also a useful diagnostic that I would not want to lose.
I don't think he's suggesting removing this... just preventing mailets from modifying it.
Mind you, I'd also like to see Spool.accept() return the message, not the key. There are exactly two calls to Spool.accept()/accept(long) in James. In both cases, we immediately follow up by retrieving the message, but we have a much more complex synchronization process because of the two stage access method.
Agreed.
But to address the fundamental challenge, I would say this is a good use of mail attributes. Sounds like we would need to provide a query interface on the repository for this, but really you want to set a date on the mail that is not last updated, but independent of any data we store right now.
-- Serge Knystautas President Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
