[Standards-JIG] Client Capabilities (rant)

Trejkaz trejkaz at trypticon.org
Sun Nov 20 21:07:34 UTC 2005

On Monday 21 November 2005 06:47, Ralph Meijer wrote:
> Now, for all optional features (plugins and/or features you can
> enable/disable), the client will have announced extensions. For example,
> it might have a plugin that implements both TINS and file transfer. It
> will insert an identifier to this end in the 'ext' attribute. For
> example 'coolplugin'. You can then send an additional disco query to the
> client that you got this extension identifier from (node#coolplugin,
> where node is the node of the caps element. Now, you should also cache
> /this/ information: coolplugin of the client node/version supports TINS
> and file transfer.

Plugins are tricky, though.  By convention they're developed by people not on 
the main client development team, so it seems there might be difficulties 
with multiple plugins choosing the same 'ext' for similar but different 
features (one might claim it has ext 'avchat', and uses TINS.  Another might 
later claim the same thing and uses Tingle.)


             Email: Trejkaz Xaoza <trejkaz at trypticon.org>
          Web site: http://trypticon.org/
         Jabber ID: trejkaz at jabber.zim.net.au
   GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F  A62C B8C7 BC8B 037E EA73
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20051121/cc1f35f0/attachment.sig>

More information about the Standards mailing list