Dnia 2012-09-14, pią o godzinie 00:15 +1000, James Wilson pisze: > It should be noted this is a hair-brained idea that has no testing or > code to back it up. > > 1) Lets just say that, for arguments sake, you have an SM instance > setup within the cluster that says: > > "I will accept ONLY high-priority resources"
I agree with Alexandre that this is a bit too complicated. The beauty of the idea we are discussing is that it takes only router to take the burden of clustering and meshing. There is no need to make other components involved and participating. But... Your idea planted some seed and I think I came up with something. Let's say, that we won't allow several SM instances handle resources of the same user. How? This needs tiny modification of C2S/SM protocol. Instead sending the user session creation request to the user domain, let's send it to the user bare-JID. This way if there is no session for [email protected] bound on example.com SMs, router will revert to routing by domain and will pick up one SM at random. Then this SM will bind '[email protected]' name and all subsequent user sessions will be created with this SM. So there will be no need for communication between SMs. (There is a possibility of race - handling several session creation requests by router and pushing to several random SMs, before first one binds user bare JID.)
