[Dxspider-support] Problems with command " dx by "

[Dirk Koopman]

On Tue, 2003-12-30 at 11:25, Darren G0TSM wrote:

> The only other command I would like to see would be SH/USER/ALL where all 
> the cluster users would be shown in alphabetical order. And there there 
> would be SH/USER G to list all G stations connected etc.
> 
> I have found that what doesnt work(if it's supposed to) is that if a user 
> has 2 connects into the network  like: G0XXX (At GB7EDX,GB7DJK) he is 
> connected to my local node, then if you sent a talk message to his remote 
> connection: Talk G0XXX > GB7DJK Hello   then the message would only be sent 
> to local user G0XXX and he would get the message:
> G0XXX de G0TSM > GB7DJK Hello
> This has happened a few times where I'd like to 'talk' to the user on his 
> other connection and it doesn't work. If I just do a talk to G0XXX then the 
> message still isn't send to both connections.
> 
> The final thing was how can a user: M1SMH (at GB7DXE, GB7EDX) not be listed 
> in the node config for GB7DXE? if I disconnect all my links he is still 
> listed M1SMH (at GB7DXE, GB7EDX) wierd.

This is all related and is an example of what I mean when I say that the
user state information is a mess and bears no relationship to reality. I
was naive (to say the least) when I thought I could model it accurately
for multiple connections.

As far as I am concerned, it isn't that I can't produce a user/node
list, it is just that the current mechanism is fundamentally broken.
This is both from the point of view of function (it doesn't do the job
in a looped network) and bandwidth (it consumes most of it).

I also believe that it isn't particularly important to know, in true
"instant" realtime, when someone is on or not.

The answer to your talk problem is to make sure that all connections get
a copy. As I propose to broadcast talk messages (actually flood route),
this would be sorted. 

Dirk G1TLH