I assume these are normal server<->server pings to keep the link alive?

If so, my main question would be "Are you sure your pong responses are correct?"
Your pong responses seem to have way more information than the pongs in my tcl-based services (please don't laugh....)...
To quote from my services' debug logs:

[03:11] DATE: Tue Dec 10 03:11:58 2002 MSG: {RECV: Bj G !1039507918.769401 channels.genericnet.org 1039507918.769401}
[03:11] DATE: Tue Dec 10 03:11:58 2002 MSG: {TestArgs=Bj G !1039507918.769401 channels.genericnet.org 1039507918.769401}
[03:11] DATE: Tue Dec 10 03:11:58 2002 MSG: {SEND: :Channels.Genericnet.Org PONG !1039507918.769401}

Obviously, I still have to convert the PONG into the correct numeric/token format, but it still works and it keeps the connection alive..... All I do is return the first timestamp from the PING to the originating server..

Hope this helps.....
Dave

At 04:37 AM 12/15/2002 +0100, you wrote:
Hello

I am trying to implement AsLL support in a service I'm writing. However,
the internal functions only allow me a precision of 3 digits in
milliseconds, whereas the servers return 6 digits in their time stamps.
I solved the problem by multiplying my own times by one thousand, then
checking the difference. Same goes for sending my own local time, here's
an example:

[RECV] AB G !1039922950.934646 K9.OpenNet.Nu 1039922950.934646
[SEND] AA Z AA AB 1039922950.934646 5049354 1039922955.984000
[RECV] AB G !1039923040.380093 K9.OpenNet.Nu 1039923040.380093
[SEND] AA Z AA AB 1039923040.380093 5040907 1039923045.421000
[RECV] AB G !1039923130.497572 K9.OpenNet.Nu 1039923130.497572
[SEND] AA Z AA AB 1039923130.497572 5064428 1039923135.562000
[RECV] AB G !1039923220.940091 K9.OpenNet.Nu 1039923220.940091
[SEND] AA Z AA AB 1039923220.940091 5074909 1039923226.015000
[RECV] AB G !1039923310.400062 K9.OpenNet.Nu 1039923310.400062
[SEND] AA Z AA AB 1039923310.400062 5067938 1039923315.468000

an output from the last ping/pong returns:

AsLL for K9.OpenNet.Nu -- RTT: 4ms Upstream: 5067938ms Downstream:
-5063ms

Does this look somewhat realistic, or am I doing it completely wrong?
(It's 4:30 AM here btw ;)

    Kind regards

  --
 Tom Rons ([EMAIL PROTECTED])
        (http://openircd.org/trons/)



Reply via email to