> 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
Ah, I didn't notice that Profile had lat/lon fields added to it :-) But I don't think storing the XMPP location in the Profile is an ideal solution. Imagine you have a laptop, and a cell phone. You leave the laptop at home signed on to XMPP, and so your SN Profile has your laptop's location stored in it. Now you go out with your cell phone, thing of the Next Big Thing, and send a notice (via SMS) to SN. That notice will have your laptop's location attached - I see that as a bad thing. Another similar scenario is if you have a desktop at work, signed on to XMPP, and a laptop at home, again signed on to XMPP. Now your SN Profile's location will bounce between the two, and any notice you create may have either location attached. If we have a table of full jid (include the resource part) and location, then we can avoid these issues. How's that sound? ~Craig _______________________________________________ StatusNet-dev mailing list [email protected] http://lists.status.net/mailman/listinfo/statusnet-dev
