Mike Hulse wrote:
>
> If all of the computer clocks in a company were set
using NTP then you would be right. But, if that is not
the case, the computer time is only as good as the
computer operator who sets the time. If you timestamp
an insert or update a record and you have an NTP server
available to you shouldn't you use it if you are at all
concerned about the accuracy of your timestamp? You
might not have +or- millisecond accuracy but if the
time is 10:54:21 and you update your record with
10:54:21 isn't that achieving your goal? :)
If you have an NTP server available, and your LAN computer clocks do not
need to be synchronized between themselves (having accurate or
inaccurate time is a different matter), as is the case because are being
set by operator, then nothing stops you from setting the time of just
your computer via NTP (ntpd, ntpdate or any sync software out there),
and simply use it. If you must do time operations with an NTP server
every time you do a db operation, then your software is in trouble.
Besides, I wouldn't trust a network that is not correctly time
synchronized :-)
Anyway, these are only usefulness caveats; if you want to do it because
you simply like all this, go for it BTW.
Carlos
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
