There's nothing stopping you from subscribing to message events. As it turns out, there currently isn't any generic subscription mechanism available, but as long as you're defining your means of distributing this information yourself, you're free to define your own means of managing subscriptions..
<message type="normal"><x xmlns="jabber:x:location"><subscribe/></x></message> Or whatever else you feel would work appropriately. On Wed, 2002-11-27 at 02:14, Arjan Peddemors wrote: > > From: Jeremy Nickurak [mailto:[EMAIL PROTECTED]] > > Sent: maandag 25 november 2002 18:45 > ... > > Personally, I'm curious why these goals couldn't be fit into > > a properly > > namespaced child element of the message packet. Could you try to > > elaborate on this some? > > Do you mean a child element of the <message/> top-level element? > To my knowledge, the distribution of <message/> elements is not based > on a subscription mechanism but on addressing. We want a subscription > based mechanism, because we do not want to send updates of context > information (presence, location, ...) to every interested party > individually. > > Arjan. > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev -- Jeremy Nickurak <[EMAIL PROTECTED]> _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
