On Mon, 1 Feb 2010, [email protected] wrote:

As long as you guard against the other cases, that could be a good
functionality.  But there's a reason it's not there now, because mostly
"server" means APRS-IS or something like it.  It's pretty important not
to even allow the user to make the mistake of connecting multiple feeds
together.  If you're gonna allow xastir-xastir server cross-gating, you have
to make sure that it isn't possible to do the other accidentally (or
cluelessly, or maliciously...).

This is very scary from a protect the APRS-INET point of view.
There have historically been problems caused by this sort of thing.
As long as this is thought about carefully and addressed, the extra
functionality of gating to RF could be a good thing in limited
circumstances.  Around here they sometimes want to gate all of the
1200-baud 2m traffic to 9600-baud 440 in order to have something
more to watch.  There are other limited uses like gating a separate
public event APRS frequency to the main frequency for the length of
an event.

--
Curt, WE7U.                         <http://www.eskimo.com/~archer>
   APRS:  Where it's at!                    <http://www.xastir.org>
  Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!"
_______________________________________________
Xastir-dev mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev

Reply via email to