On Fri, Feb 18, 2011 at 14:22, Sasha Dolgy <[email protected]> wrote: > One more clarification. The JCR work in Vysper > (org.apache.vysper.storage.jcr) is to use JCR as a storage provider for user > management, roster management, etc. ?
yep. but I'm not very happy with them. Bernd > > On Fri, Feb 18, 2011 at 1:29 PM, Bernd Fondermann < > [email protected]> wrote: > >> On Fri, Feb 18, 2011 at 13:15, Sasha Dolgy <[email protected]> wrote: >> > Hi Bernd, >> > >> > I had a look at >> > org.apache.vysper.xmpp.state.resourcebinding.ResourceRegistry ... so the >> way >> > Vysper currently works today is that all sessions are stored in memory? >> If >> > vysper instance crashes, the resource id : session relationships aren't >> > persisted anywhere? >> >> No they aren't. But since XMPP uses long-living TCP/IP connections, >> recovery from a server crash is equivalent to a >> client/server-reconnect anyway. >> This does not impose practical problems. (Leaving a reverse proxy setup >> aside.) >> However, a cluster of XMPP servers for the exact same domain(!) would >> need to share the ResourceRegistry datastructure. >> (You could also have a federation of XMPP servers, but that'd mean >> different users might have different account names like >> [email protected], [email protected].) >> >
