[Dxspider-support] Talk command
Aurelio, PC5A/AA2WH
aurelio at esrac.ele.tue.nl
Wed Jul 11 21:32:20 CEST 2007
On Wed, 11 Jul 2007, Dirk Koopman wrote:
<snip>
>
> However, that then means that you can't be sure that the recipient
> actually either is connected somewhere or even exists.
>From a user point of view it's best to know immediately if the receipient
of a talk is connected to the network. Otherwise it will be confusing and
may even lead to send an announce.
>
> The protocol does not get a complete picture of the network until about
> one hour has passed (it may be less, but not more). This means we have
> to make a choice: either allow a "broadcast" to find the recipient or
> only do a "directed" talk if the recipient is in the routing table.
If it takes up to an hour before all connected users are known to the
network, so be it. If users are normally hidden from the network this may
have a reason (isolated node, RF link etc..). In that case you would not
want to receive talks anyway.
If the new protocol aims in reducing the number of talk like announces
then probably the broadcast type of behaviour is in place. Still no
guaranties that a talk will be delivered succssfully unless ALL nodes use
the same new protocol...
73 Aurelio
More information about the Dxspider-support
mailing list