Le 17/09/2012 15:39, Tomasz Sterna a écrit :
Dnia 2012-09-17, pon o godzinie 14:29 +0200, Alexandre Jousset pisze:
I see a possibility for this but it looks hackish...: router
looks into the messages when there are more than 1 possible recipient
component (in "user@domain" case). If it is an IQ => it generates the
error itself. Or it passes the message to one of the component (at
random) that will generate the error message...
I would like to keep the current separation, that router does not have
to know XMPP-IM at all. It shouldn't be inspecting content of the
package.
Implementing XMPP-IM is a job of SM component (and C2S a bit).
I know and I understand, this is why I said I didn't like these
solutions. I thought about them because there are some cases where the router
looks into the messages. Maybe not sending the error message but forwarding the
message to only one SM could be possible without breaking too much that rule...
But it's not perfect, I know.
I'm still trying to think about a better solution.
What's wrong in pinning all user sessions to one SM instance?
Nothing, except race condition... I'm still thinking about how to
resolve this issue too... It would be a much nicer solution I agree.
--
-- \^/ --
-- -/ O \--------------------------------------- --
-- | |/ \| Alexandre (Midnite) Jousset | --
-- -|___|--------------------------------------- --
