You're right, and it's one of the reasons why I mentioned that this does
not make sense.
NTP is a time system designed for high-accuracy synchronization of
computer clocks, preferably sub-millisecond precision. You get the time
not only from one place but from several, and your NTP server must merge
these different times in a non-trivial way.
So it is useless to have such a servlet. You get better precision if you
have your clock NTP-synchronized and simply print the date&time. Even
building an NTP service is probably not for Java (at least not for
present Java), as it requires to be so close to the hardware.
Sure that the original poster will find a more useful thing to do as a
Java servlet. There are so many...
Carlos
Danny Ayers wrote:
>
> Hi,
> this may be a stupid question, but what is there to ensure you get the
> data in good time? - if it takes a minute to read the stream, then we're
> not talking atomic clock accuracy.
> Cheers,
> Danny.
___________________________________________________________________________
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
