Dnia 2012-09-14, pią o godzinie 15:50 +0200, Alexandre Jousset pisze: > 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.
But the only parameter to take into consideration when deciding which resource gets the message is priority. There is nothing in XMPP about delivering to most recent resource. I would like to stick to the specification :-) -- Tomasz Sterna Instant Messaging Consultant : Open Source Developer http://tomasz.sterna.tv/ http://www.xiaoka.com/portfolio
