This time between the <contexts/> from the Gateway being compared with
the Geo-Matcher's Locations table. The problem is on the <contextions/
> side.
This one is a little bit tougher than the Voozer's buddy list merge.
In this case the Geo-Matcher has two tables to contend with: the
locations, and the relations. When the incoming interfaces were at
the ME it was pretty straight forward - if a TTL was 0 simply drop
_that_ user's context registration from Locations and sweep the
Relations table for the Locations ID that was dropped.
It is going to take me a little bit to thinking this through and come
up with an efficient way to have the <contextions/> message sent back
to the Gateway. I think I really want to separate Relations table all
together from this equation and come up with a simple "repaint"
mechanism for telling the <contextions/> message to be built and sent.
Kit
_______________________________________________
users mailing list
users@...
http://lists.rvooz.org/listinfo.cgi/users-rvooz.org
