[aprssig] Danger Will Robinson!
kg4wsv at gmail.com
Wed Jul 22 16:39:30 CDT 2009
On Wed, Jul 22, 2009 at 4:30 PM, Stephen H. Smith<wa8lmf2 at aol.com> wrote:
> Given the constant rapidly-changing status of these objects, and the VERY
> TRANSIENT nature of this information, I would think it would make sense to
> propagate the latest Echolink status reports through the APRS-IS in real
> time, but NOT archive, cache or save them in any way.
> This would eliminate the caching/archiving/storage burden on the APRS
But not the bandwith issues. See the previous post comparing this
proposal to CWOP, which had to split into another IS network because
of the load.
IMO, this is something that should be handled at the local level,
maybe between the echolink node operator and the local Igate operator.
More information about the aprssig