Re: Synchronizing on File Formating

Thanks for your reply, Frank!

>> B. Password Life Time
>> It is open in format definition whether this field expresses a 
>> timepoint  or a time span. I assume the former.
>>
>> --> I am using an "epoch" timepoint for values
>>
>
> IIRC, no implementation supports this field yet, so go ahead, make a
> decision, and document it. My preference for this field would be a
> time difference in seconds. That would make the field independent of
> the last modification time. E.g., it could be 90*86400 if the password
> expired after 90 days. 


I'm not sure I understand. Did you mean "That would make the field 
*dependent* of
the last modification time." ? Because that is what would have to happen 
if you suggest a time span. I see an advantage in making it a time point 
because  a) points could be calculated by application on demand (e.g. by 
offering a selection of previous or standard distances), whereas b) 
points could be also fixed by user input (say you got a specific date 
posed by your chief-in-office), and c) points can be displayed and 
compared more easily where points are required (e.g. list of expiry 
dates etc.)

In fact my library would not have to make necessary assumptions on the 
nature of this value, but I would strongly prefer to offer an 
interpretation in place of "to be seen later". ;)

- Wolfgang





-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf