Rationale behind explicit setLastUpdated in MailImpl writeobject sought.

[S�ren Hilmer]

Hi,

During my implementation the multiple delay times in RemoteDelivery, I have 
run into a little problem.

My idea was to always do an outgoing.accept(0) and set the Mails lastUpdated 
to currentTimeMillis+the next delay for that mail-

But alas in 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? 
Does it actually make sense to have a setLastUpdated method, when the effect 
of it is changed behind your back?


-S�ren

-- 
S�ren Hilmer, M.Sc.
R&D manager             Phone:  +45 70 27 64 00
TietoEnator IT+         Fax:    +45 70 27 64 40
Ved Lunden 12           Direct: +45 87 46 64 57
DK-8230 �byh�j          Email:  [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]