Hi,
Le 13/09/2012 16:15, James Wilson a écrit :
I've been watching this discussion unfold and thought I might contribute.
Thanks for your contribution.
Personally, I have not ran a jabberd2 instance in a long time, but this
question below:
On 13/09/2012, at 11:35 PM, Tomasz Sterna wrote:
Dnia 2012-09-13, czw o godzinie 15:07 +0200, Alexandre Jousset pisze:
But then - what happens if two resources of the same priority get
connected to two different sm instances?
*This* was my real question ;-)
I don't have answer.
Will have to think about it.
leads me to believe that they should act like so:
[...]
I don't know if this would work in practice, but this is one way I see the
issue of the above question being resolved.
I don't know what Tomasz thinks about this, but I think it is quite
complicated for just that case.
I was thinking about another idea: AFAIK the protocol says that in that case
the message should either be duplicated, and we've seen previously that this may lead
to problems (IQs, ACKs), or sent to one of the recipients based on the
implementation's choice. Maybe we can just record the time when the session was
started and add this information to each related <bind> request, keep at router
level that information in the hash table values' structure, and use it in that case.
The message would then be delivered to the recipient of the most recently started
session.
...?
--
-- \^/ --
-- -/ O \--------------------------------------- --
-- | |/ \| Alexandre (Midnite) Jousset | --
-- -|___|--------------------------------------- --
