Ashish wrote: >> Thanks for the suggestion. Acutally, a tree-like structure would make >> sense since there are collection nodes (which I didn't plan to >> implement in the first round) and "leaf" nodes. We're also discussing >> persistence services of Vysper within the Labs JIRA >> (https://issues.apache.org/jira/browse/LABS-354). >> >> A node is nothing special, you could visualize it as a "virtual user" >> relaying messages sent to it, but of course it has to store a >> configuration etc. > > This reminds me of an interesting implementation. Its the infoq.com > site implementation, and the site has a presentation on that > (http://www.infoq.com/presentations/design-and-architecture-of-infoq) > > What they did was, they created a Hibernate like means POJO based > layer for JCR (Jacrabbit). We can plan for a similar implementation. I > don't recall the complete details. We may derive some good practices > from it.
Interesting. The current storage for Vysper is based on Jackrabbit, too. But it is not fixed to Jackrabbit. For example, you can just switch to in-memory storage for roster and user auth, which of course does not survive a restart. Vcard-temp storage is JCR only, but as soon as somebody adds another impl, you can change that, too. Bernd
