Craig Andrews wrote:
I was thinking that we could create a new, 3 column table: jid, updated,
location. When our XMPP bot receives a location update, it writes to the
table. When an XMPP message is message sent to the bot to create a notice,
we read the table, look up the jid, and if the location data isn't too old
(we'd need to figure out a reasonable max age), attach that location as
the notice's location.
How does this approach sound?
The profile tables contains location information already, and that's
used for new notices if they don't have location data attached.
So maybe just let XEP-80 data update the profile table instead? I can
don't see much value in having two different locations for the same user.
-Evan
--
Evan Prodromou
CEO, StatusNet, Inc.
[email protected] - http://identi.ca/evan - +1-514-554-3826
_______________________________________________
StatusNet-dev mailing list
[email protected]
http://lists.status.net/mailman/listinfo/statusnet-dev
