[Standards-JIG] proto-JEP: Flagging the Primary Resource

Trejkaz trejkaz at trypticon.org
Thu Sep 29 17:21:42 CDT 2005


On Fri, 30 Sep 2005 08:16, Ian Paterson wrote:
> I was interested if anyone sees any reasons not to do it this way
> instead.

Ah.  Well, there is probably some middle ground that can save us some presence 
space.

If there is only one resource online, don't send the extension.  If there are 
more than one, send it.  In the case you described when resource2 comes 
online with the same priority and clients might misunderstand, send the 
primary flag with resource1's presence, _before_ sending resource2's 
presence.

Once all that's done, you have minimal XML for most users who don't even know 
what a resource is, but still have trivial rules for clients to figure out 
who is the primary resource.

TX

-- 
             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/20050930/502847dd/attachment.pgp


More information about the Standards-JIG mailing list