[aprssig] IGATE message routing bug?

[Jim Alles]

Pete, thank you for the reply.

Sorry, sometimes I get stuff bass-ackwards.
Part of my confusion is that some explanations left scattered around seem
to indicate a race condition, where you and Lynn (and, I am sure others)
have made it clear that there is none.

73,

Jim A.

On Sun, Nov 20, 2016 at 3:11 PM, Pete Loveall AE5PL Lists <
hamlists at ametx.com> wrote:

> See below...
>
> > -----Original Message-----
> > From: Jim Alles
> > Sent: Sunday, November 20, 2016 2:05 PM
> > Subject: Re: [aprssig] IGATE message routing bug?
> >
> > Can anyone tell me if the the UDP/HTTP port or the qAO construct is
> available
> > for use in any client software?
>
> There are a number of smartphones apps that use the UDP and HTTP ports as
> well as javAPRSSrvr being used as a SATGate (why those ports were
> originally developed).  The qAO construct is available for all client
> software but whether they use it or not is an issue that will be difficult
> to ever get agreement on.
>
> > Does the server duplicate checking really happen to a packet before
> insertion
> > into the connected clients' heard list?
>
> No, I stated the exact opposite!  Server dupe checking is done -after- any
> client-specific processing is done.  Client-specific processing includes
> updating its last-heard list.
>
> Hope this helps.
>
> 73,
>
> Pete Loveall AE5PL
> pete at ae5pl dot net
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20161120/68a3eb91/attachment.html>