Order Tray | Contact Us | Home | SIG Lists

[aprssig] POI engine on APRS-IS (no engine required!)) (wrong)

Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.to
Tue Feb 21 16:36:48 UTC 2012


Keep the POI server that puts the object at the most recently received 
posit of the sender, forget the change to the Item-as-Message  but have 
the POI server use that as the confirmation response to the object 
creation with the ACTUAL lat/lon used for the object.

Retransmission of the object after the originator has moved can be 
handled by the POI server doing a dupe-detect on the defining request to 
keep the object where it was for a given message sequence.  If the owner 
initiates a new transmission, the sequence will change and the object 
will move to the new location because the new message came from the 
current owner of the object.

I still contend that we need an explicit ADOPT flag to prevent 
inadvertent movement of objects between users across the global scale.  
Just because one event has a FOOTSORE object, a new FOOTSORE object 
somewhere else on the planet should NOT automatically move the object 
unless the new owner really intended the adoption.

Automatic creation of existing object is especially bad in the UI-View 
world because we just built an easy way for someone to completely ERASE 
the original object definition in the UI-View instance because it will 
REPLACE its current definition with a received re-definition (adoption) 
instead of simply stopping transmission of its locally-defined object of 
the same name.

Adoption is good at the local level (maybe), but when the object 
definitions hit the global APRS-IS, things get ugly fast.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32


On 2/21/2012 11:25 AM, Bob Bruninga wrote:
> My Bad.  You are right!
>
>>> But what LAT/LONG should be used for the wildcard?
>> It uses the present address of the sender when the
>> ITEM-in-MSG message is created.
>>> if you use the current position then you can only
>>> create objects that follows the sender.
>> No, they remain or are deadreckoned from where they were first entered.
> I WAS WRONG, You are right! since each new incoming message will have the
> sender has moved.
>
> OK, we have towork around this.
>
>
> Bob, WB4APR
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>




More information about the aprssig mailing list