[Standards-JIG] JEP-0166 - Jingle Resource determination

Peter Saint-Andre stpeter at jabber.org
Mon Feb 13 22:34:20 UTC 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Naturally we'll have to be careful to not leak presence information. If
you try to start a Jingle session with me via my bare JID but you're not
in my roster, the server needs to ask me if that's OK or send the
request to my most available resource for that session type (per RAP).

Peter

Joe Beda wrote:
> You are right -- it should be possible for the server to proxy the
> connection to the appropriate resource if there is support.  I'd like to
> get a section on this into the spec before it is final.  Along with
> this, I'd like the server to be able to bow out of the transaction and
> have the endpoints start talking between themselves. 
>  
> I'd also like to sketch out more intersting server scenarios such as
> calling one resource after another (say every 30 seconds) or ringing
> more than one resource at the same time.
>  
> Joe
> 
>  
> On 2/5/06, *Joe Hildebrand* <hildjj at gmail.com <mailto:hildjj at gmail.com>>
> wrote:
> 
>     I think the idea was that RAP could help with this:
>     http://www.jabber.org/jeps/jep-0168.html
> 
>     On Feb 2, 2006, at 9:23 PM, Vinod Panicker wrote:
> 
>     > Hi,
>     >
>     > In the Jingle spec, the responsibility for Resource determination is
>     > put on the client.  This goes against the rationale of xmpp having
>     the
>     > server do most of the logic.  Also, with bandwidth constrained
>     > clients, this resource determination takes a bit of time.
>     >
>     > Can't we move this to the server?
>     >
>     > Regards,
>     > Vinod.
> 
> 
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD4DBQFD8QlsNF1RSzyt3NURAtFGAJj4JXrnGFuNHQI9hSrdCjBmFuSSAKCIsjcF
8Fm4I6qR7E3mzR09iSDabA==
=Wc4i
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060213/e22e00eb/attachment.bin>


More information about the Standards mailing list