[aprssig] APRS-IS Database :: Query for static dataset
kg4wsv at gmail.com
Tue Jul 21 18:45:22 CDT 2015
On Tue, Jul 21, 2015 at 6:14 PM, Paul Bramscher via aprssig
<aprssig at tapr.org> wrote:
> Is it the t2 servers that do the de-deping?
Thin about it - the core was doing dedup before T2 existed...
> If I submit a packet to
> "rotate" that ends up going to "first" and my neighbor does the same,
> but a second or two later, I understand that it will be deduped.
> But if the guy a mile or to away ends up submitting the same packet to
> "second", how is the deduping behavior there going to be aware of what
> happened on "first"?
_Any_ server that gets 2 copies of a packet drops one.
> Is there a final round of de-duping on the core
> APRS servers?
Deduplication happens at every level. If igates A and B are
connected to one.t2.net (which is connected to second.aprs.net), and
igate C is connected to second.aprs.net, then only one copy leaves
one.t2.net and only one copy leaves second.aprs.net. Which copy
survives depends on which got there soonest. And possibly where the
client viewing the data is connected. (Client X-ray connected to
one.t2.net and client zulu connected to second.aprs.net could see
different copies, depending on time of arrival at the servers.)
More information about the aprssig