Alexandre, Ha! I thought this was perhaps a little more complex then needed, but then again, I've never been one for 'simple' solutions. :)
Your suggestion sounds really good, and would seem to work given that the most recently-started session seems to be the most logical data-object to use. -James On 14/09/2012, at 11:50 PM, Alexandre Jousset wrote: >> ... > > 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 | -- > -- -|___|--------------------------------------- -- > >
