[Xastir-dev] Messaging, acks, UI-View quirks

[Curt Mills]

On Sun, 12 Dec 2004, Tom Russo wrote:

> One thing he did show me was what happens if he attempted to send me messages
> with "{" in the body (not legal per APRS spec).  Xastir took the first five
> characters after the { and acked as if that were the message number (which
> appears to be the correct thing to do), and it was all a big mess because
> his actual message ID never got acked.

That's ugly!


> So UI-View scans for the *last* { in a message and uses the next chars as
> the message ID, xastir scans for the first.
>
> I don't know that there's anything to do about that --- as I read the spec
> it appears that Xastir's doing the right thing and having { in a message other
> than the one preceding the message id is an error --- but it's something to be
> aware of and perhaps it's desirable to change it?

Yea, we should change in that case.  UI-View can't be fixed.
Xastir is doing it per the spec, but we can change, still be per the
spec, and interoperate better with UI-View.  Seems like a win-win.

-- 
Curt, WE7U.				archer at eskimo dot com
http://www.eskimo.com/~archer
  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!"