[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jabber-jdev
Subject:    RE: [JDEV] jabber extensions available for handling locationinfor
From:       Joe Hildebrand <JHildebrand () jabber ! com>
Date:       2002-11-29 16:55:14
[Download RAW message or body]

I'd prefer that it work with existing server implementations.

Both the .org and .com servers reject packets that aren't
iq/message/presence with a "400 Bad Request" error.  Since it's unlikely you
are going to talk many server vendors into adding a new top-level element
for this purpose, I'd suggest choosing the existing packet type with the
closest semantics, and just using it.

That being said, of *course* you can write a non-standard server, or, if you
follow the license that came with the source code, add it to an existing
implementation.  Just don't expect to be able to interoperate.

-- 
Joe Hildebrand


> -----Original Message-----
> From: Arjan Peddemors [mailto:Arjan.Peddemors@telin.nl]
> Sent: Thursday, November 28, 2002 6:36 AM
> To: jdev@jabber.org
> Subject: RE: [JDEV] jabber extensions available for handling
> locationinformation
> 
> 
> Yes, this could very well work, although for "protocol
> cleaness" I'd prefer to have presence at the same level as
> location (maybe also as part of <message/>). From a context
> information point of view, presence and location ar similar.
> The nice part here is that it would be relatively simple to
> add other kinds of context information (temperature, social
> setting, acceleration, ...). Of course, a pubsub component that
> is generic, flexible, and fully integrated with the jabber
> server must be in place...
> 
> Arjan.
> 
> > From: Joe Hildebrand [mailto:jhildebrand@jabber.com] 
> > Sent: woensdag 27 november 2002 21:55
> ...
> > Yes, something like this:
> > 
> > <message to='pubsub'>
> >   <location xmlns='http://.../location'>
> >     <lat>39.75</lat>
> >     <long>-105</long>
> >   </location>
> > </message>
> > 
> > where 'pubsub' is the name of a component that would 
> > redistribute this to all of the interested parties.
> 
> _______________________________________________
> jdev mailing list
> jdev@jabber.org
> http://mailman.jabber.org/listinfo/jdev
> 
_______________________________________________
jdev mailing list
jdev@jabber.org
http://mailman.jabber.org/listinfo/jdev
[prev in list] [next in list] [prev in thread] [next in thread]