[aprssig] Msg reply path

[Andrew P.]

On a tangent from this, is there ever a reason to _initiate_ a message with either a WIDEn-N or SSn-N alias where N < n? I've seen cases like WiDE1-1,WIDE2-1, but are there any other cases that make sense (except possible smart reverse-pathing where it is obvious that the whole n wasn't needed)? Should digis that support SSn-N also support SSm-M where 1 <= m < n?

Just a thought to stir the pot.

Andrew Pavlin, KA2DDO
------Original Message------
From: Stephen H. Smith
To: aprssig at tapr.org
Sent: Oct 6, 2013 10:23 AM
Subject: Re: [aprssig] Msg reply path


On 10/6/2013 7:21 AM, Keith VE7GDH wrote:
 > Stephen WA8LMF wrote.
 >
 >> UI-View just blindly re-sends an unacked message a fixed number of times at constant time intervals (default is 5 tries 40 secs apart) and then gives up.
 >
 > But it is easily configurable to change the retry interval and the number of tries,
 
 But that doesn't fix the fundamental flaw of lacking the decaying-rate retry 
 algorithm that makes more efficient use of the channel.
 
 (This can be fixed by using the UIview plugin  "UI-Instant Messenger", a 
 replacement messaging client for UIview,  that DOES do the decaying routine 
 correctly.)
 
 
 _______________________________________________
 aprssig mailing list
 aprssig at tapr.org
 http://www.tapr.org/mailman/listinfo/aprssig
 

Sent from my Verizon Wireless BlackBerry