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

Joe Beda jbeda at google.com
Mon Feb 6 14:37:54 UTC 2006

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.


On 2/5/06, Joe Hildebrand <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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060206/cd9437c6/attachment.html>

More information about the Standards mailing list