[aprssig] Paths - Solution proposal
david at davidandrzejewski.com
Sun Jul 13 10:01:36 CDT 2014
I'm not sure how I feel about Mark's solution, but just for sake of
argument, perhaps there's a compromise.
Warning: This would make things confusing for users.
Let the users specify the path as they do today - this maintains
compatibility with everything that currently exists. New or upgraded
digis could have this new logic in them, and if they do, they can ignore
the path and try to determine what's best for the network at that
moment. This would be a good transitional phase.
An analogue to this is multi-input voice repeater systems. You've got
some out there that allow the user to manually select which input they
use, usually via PL tone. Others use a voting comparator, and they
determine which input gets used automatically - the onus is not on the
end user to make decisions, the repeater "just works."
On 2014-07-13 10:50, David Flood wrote:
> While your ideas would work if we were starting from scratch, it will
> probably fail as a redesign due to two reasons:
> 1) It makes the same fatal assumption that almost every computer
> is making these days, that everyone has (or can afford) the most modern
> hot-rod hardware available.
> 2) That all deployed hardware is junk and should be replaced
> Just as in the computer world not everyone has 64 Gig of RAM (but every
> programmer writes as if they do) and a video system that supports
> resolutions normally only seen in stadiums, not everyone in the Ham
> wants to buy, configure, and mess with the equivalent of a Raspberry PI
> a TNC-PI and radio attached.
> -----Original Message-----
> From: aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] On
> Of Mark Cheavens
> Sent: Sunday, July 13, 2014 6:54 AM
> To: TAPR APRS Mailing List
> Subject: [aprssig] Paths - Solution proposal
> With modern TNC's available there is no reason not to start working on
> modern solution.
> aprssig mailing list
> aprssig at tapr.org
More information about the aprssig