[pskmail] Re: Python Client Testing and Stream IDs
- From: William <va3udp@xxxxxx>
- To: pskmail@xxxxxxxxxxxxx
- Date: Mon, 10 Nov 2008 16:51:11 +0100
Le 08-11-10 à 16:33, Rein Couperus a écrit :
William, you did not look closely enough :)
Could be :) But I think there may be something funny going on.
The comment I refer to is this one in arq.pm:
############################################################
sub ttyconnectblock { # Connect (caller:port, my:port)
# c block = Caller:port My:port <streamnr. (0)> <max. blocklen>
# e.g.: '00cEA3FG:87 PI4TUE:87 4'
############################################################
The "c block" line comes from page 3-4 of ARQ2.pdf but the
example immediately below it drops the stream number.
TX (2008-11-10 15:20Z): <US><SOH>00cPA0R:1024 PI4TUE:24 5F258<EOT>
RX (2008-11-10 15:20Z): t t O<US><SOH>0#kPI4TUE:24 PA0R:1024
53336<EOT>
A problem I see when done like this is that the client cannot
pick it's own stream number - The client might want to use %,
and the server should send packets with that as the second byte.
When the client sends packets to the server it would use #.
If a client wanted to make multiple connections to the server,
or to multiple different servers, there would be no way to
distinguish the streams I think. Especially in later packets
that don't necessarily carry the callsigns.
Or do I misunderstand?
73 de William EA5/VA3UDP
va3udp /@/ rac.ca
Other related posts:
