Quoting Vijay <[EMAIL PROTECTED]>:
> Thanx for ur valuable comments & corrections
> The Protocol suggested by you looks good, but I have some queries
> related to
> changes suggested ...
> You seem to be using a unique resource for each application/add-on.
> Who is taking care of routing the messages to each
> application/add-on.?
> So, is every application is logging into server with difference
> resource
> with the same user?
> Does this mean a separate socket connection to jabber server for each
> application/add-on is needed?
Hrm, you're correct, poor example. This would be if a seperate application
actually connected to the server, providing capabilities. Really, the way
people are looking at using it to see what a client is capable of is using the
<ns> tag, as WinJab currently does. Example:
<iq type='result' id='browser_JCOM_7' to='[EMAIL PROTECTED]/Work'
from='[EMAIL PROTECTED]/Work'>
<user xmlns='jabber:iq:browse' jid='[EMAIL PROTECTED]' name='tcharron'>
<ns>jabber:iq:roster</ns>
<ns>jabber:iq:last</ns>
<ns>jabber:iq:version</ns>
<ns>jabber:iq:time</ns>
<ns>jabber:iq:browse</ns>
<ns>jabber:iq:conference</ns>
<ns>jabber:iq:autoupdate</ns>
<ns>jabber:iq:filter</ns>
<ns>jabber:iq:oob</ns>
<ns>jabber:x:delay</ns>
<ns>jabber:x:oob</ns>
<ns>jabber:x:roster</ns>
<ns>jabber:x:signed</ns>
<ns>jabber:x:encrypted</ns>
<ns>jabber:x:autoupdate</ns>
<ns>jabber:x:conference</ns>
</user>
</iq>
My example was basically a way to have a seperate resource defined as an
application. The above is probrably the best way to handle it, and declare
your data as being a namespace, such as jabber:x:i3connectgames
---
Thomas Charron
<< Wanted: One decent sig >>
<< Preferably litle used >>
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
