It's generally considered bad to overload <presence>. This is because it is the only current element that the server rebroadcasts. For people with large rosters this can be a lot of information the server then has to push out. If there is a strong technical reason that it needs to be in <presence> I would suspect you would be interested in the current discussion about pubsub in Jabber. You can find more on the standards jig mailing list. Does that help you find a better fit?
--temas On Wed, 2002-04-10 at 11:17, Henry Minsky wrote: > > I am working on a project where we have a server that is tracking users' > locations > via various technologies, and recording them in a realtime database. > > I would like to be able to annotate each jabber user on the server with > some information about their physical location. This information would most > likely be > retrieved in the presence information for each user, although might there > be some better place to put it, such as a new separate iq query? > > Note that the clients themselves do not necessarily know their own locations, > that information is derived on the server, so I need my "location server" to > somehow inject the location information for each user into the jabber > server, where it can be accessed by custom clients, or perhaps also stuffed > into the english-readable status strings, for backward compatibility with > existing > clients. > > Anyone else working on something like this? > > Thanks, > Henry Minsky > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
