A few thoughts inline.
На 01.12.10 22:25, Conrad Beckert написа:
My idea is - to allow something like that with different resources
too. (sorted by priority) That would be nice as e.g. Empathy doesn't
The same goes to Jingle. Sometimes I leave home without closing
Empathy. Without jugglig with priorities there is no way to recieve
calls. (as it gets the highest priority or the longest connected)
The strange thing is, that the other side (supposed it is on SC)
might not notice the fact, that I'm connected twice. Not even contact
details shows that.
What do you think?
The patch that I was referring to in my previous e-mail made SC direct
the call to the resource that has highest priority *and* that also has
jingle capabilities. This is why your GMX problem shouldn't happen again.
XEP-0208 seems to be implying that this is the recommended procedure
although I am not sure if any XEP actually defines it as a best practice.
I agree that this may lead to confusion in some cases (e.g. if a client
does not auto-decrease its priority after inactivity). Still, I am not
sure it would be a good idea to expose users to resource IDs.
Google for example add an arbitrary string to your resource and showing
that to users wouldn't really help them determine whether or not the
resource would be a good one to call.
Besides implementing resource selection for calls in SC's GUI, while
totally feasible, would require a non-negligible effort so I don't think
we are likely to see it in the following weeks.
In the SIP world, many providers would fork inbound calls to all
currently registered clients. This was probably driven by the initial
lack of a resource id equivalent in SIP (GRUUs only came later) but
still the outcome is good for users.
Google (again) would currently do the same with inbound IMs so it is
probably not unreasonable to expect that they, and others, may one day
also start doing it for jingle IQs.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org