Let me know if you have success with the client.
The NTP client in the Service uses the standard NTP timestamps to
account for network lag when talking to the server as well... you
should always get the accurate atomic time.
Richard
On Mar 5, 2:28 pm, Mark Murphy wrote:
> Richard Schilling wr
Richard Schilling wrote:
> When you connect to the service, you register a callback. The service
> updates your callback object with calls to two methods, onTimeUpdate
> and onClockStateChange.
>
> The service passes to void onTimeUpdate(long atomicTime, long
> localTime); two parameters:
>
> 1.
I just double checked. It works for me too. You may have hit it
earlier when I was updating the web page.
To answer the question:
How are you handling the overhead of IPC in your time calculations?
When you connect to the service, you register a callback. The service
updates your callback obj
3 matches
Mail list logo
