Stephen Pendleton
07-30-2008, 08:18 PM
-----Original Message-----
From: mobile-bounces (AT) xmpp (DOT) org [mailto:mobile-bounces (AT) xmpp (DOT) org] On Behalf Of
Mickaël Rémond
Sent: 07/30/2008 11:57 AM
To: Going Mobile with Jabber/XMPP
Subject: Re: [mobile] Cell IDs over XMPP?
The idea is to map on the server, yes. You know the few cells that represent
the office for example. Then, you can map it to the "at office" location on
the server side, without having to map that on every cell phone in the
company.
You can then, have a screen for the secretary that can get the list of
people at the office for example. No need to have much intelligence in the
client for that.
O K, what you are describing similar what I do, but using a different
method. What happens in my case is the client device obtains the cellid and
transmits to to the server, and then the mapping is done by the server to
obtain the lat/lon which is then sent back to the client. From then on, the
lat/lon is used.
I find this useful for my application since I have methods of translating
cellid and also wifi access point sid's to lat/long, so I can stick to just
using lat/lon for location updates.
I think it would be more natural to add this to XEP-0080 rather than adding
YAX (yet another xep!). After all, all the cases I can think of would use
the cellid for geoloc.
From: mobile-bounces (AT) xmpp (DOT) org [mailto:mobile-bounces (AT) xmpp (DOT) org] On Behalf Of
Mickaël Rémond
Sent: 07/30/2008 11:57 AM
To: Going Mobile with Jabber/XMPP
Subject: Re: [mobile] Cell IDs over XMPP?
The idea is to map on the server, yes. You know the few cells that represent
the office for example. Then, you can map it to the "at office" location on
the server side, without having to map that on every cell phone in the
company.
You can then, have a screen for the secretary that can get the list of
people at the office for example. No need to have much intelligence in the
client for that.
O K, what you are describing similar what I do, but using a different
method. What happens in my case is the client device obtains the cellid and
transmits to to the server, and then the mapping is done by the server to
obtain the lat/lon which is then sent back to the client. From then on, the
lat/lon is used.
I find this useful for my application since I have methods of translating
cellid and also wifi access point sid's to lat/long, so I can stick to just
using lat/lon for location updates.
I think it would be more natural to add this to XEP-0080 rather than adding
YAX (yet another xep!). After all, all the cases I can think of would use
the cellid for geoloc.