[JDEV] adding new buddies

[Thomas Muldowney]

There is a very good reason to this.  The roster is designed to be a place to keep almost an address book
of people that you want to communicate with.  You don't even have to subscribe to people to put them into
the roster.  You could just store info there in an address book style.  Presence on the other hand is
completely designed around the concept of availability, and therefore the subscribe to that availability
needs to be in that area.  I hope this clearly explains the fundamental theory behind all of that.

--temas

On Tue, Aug 29, 2000 at 11:01:45AM -0700, Robert Temple wrote:
> I don't understand why the <persence type="subscribe"> packet is used to ask to subscribe to someone's presence.  IMO it would be a lot more intuitive and useful if the <query xmlns="jabber:iq:roster"> packet provided this function.
> 
> Already, the <presence type="subscribe"> packet is linked with the presence packet.  For example, if I send a <presence type="subscribe"> packet, I get back one or more "jabber:iq:roster" packets.
> 
> Couldn't the server handle a packet like:
> <iq type="set" ...>
> <query xmlns= "jabber:iq:roster">
> <item ask="subscribe"...>
> ...
> 
> the same way it currently handles the 
> <presence type="subscribe"> message?
> 
> and then instead of returning a 
> <presence><status>Not Found</status>... packet when the person doesn't exist, it could return back a
> <iq type='error'/ ...> message and one would expect.
> 
> -Robert
> 
> ___________________________________________________
> GO Network Mail                                    
> Get Your Free, Private E-mail at http://mail.go.com
> 
> 
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20000831/97eb31b3/attachment-0002.pgp>