[947] in SIPB bug reports
[jefft@ATHENA.MIT.EDU: xzwrite ping bug]
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Mon Mar 12 17:06:43 1990
Date: Mon, 12 Mar 90 17:06:18 -0500
From: Barr3y Jaspan <bjaspan@ATHENA.MIT.EDU>
To: bug-sipb@ATHENA.MIT.EDU, jefft@ATHENA.MIT.EDU
The man page states that the $message will be == "PONG\n", however,
currently, the PONG is being sent on field $1. Which is the signature
field, I believe, in any case the message field is blank.
Either the man page or the program is wrong.
Nope, sorry; you are wrong. The $message field is, in fact, set to
"PONG", and yes, it is field $1 in .zwgc.desc. Your confusion lies in
the fact that you believe that $1 == the signature field and $2 == the
body of the message. This is a convention used by zwrite when sending
normal messages, but there is nothing "special" about it. The PONG
message of xzwrite is not a normal message and there is no good reason
to waste bandwidth sending a signature for a message that should never
be displayed.
There *was*, in fact, a bug -- xzwrite was setting the length of the
PONG message to 5 instead of 4, and zwgc was converting the extra null
byte to a newline (\n), which is why you had to match against "PONG\n"
instead of "PONG". I just fixed this.
The new xzwrite will replace the current version Real Soon Now.
Barr3y
