On Sat, Apr 19, 2008 at 11:31 AM, Gerolf Seitz <[EMAIL PROTECTED]> wrote: > disclaimer: i have practically no dev-experience with both JCR and XMPP. > feedback of people familiar with JCR is very much appreciated. > > so how about something like this: > /content > /jids > /<JID> // bare jid > /roster > /<JID> [ask] [subscription] [name] > /groups > /<group> > > > [ask], [subscription], [name] are considered properties of a roster item.
Looks good. > > besides roster management, what else do we have to persist wrt: - overall server persistence login information (essentially password) credentials logs, events, errors, statistics server configuration > -RFC3920 > -RFC3921 > -any important XEPs with "high" priority > ? I would not model any persistence for specific XEPs yet. One requiring persistence is Multi-user chat (XEP-045), another one is Flexible Offline Message Retrieval (XEP-0013). -- Concerning the generally structure you started to outline: an alternative approach to /content/jids/[EMAIL PROTECTED] could be using the reverse domain scheme /content/jids/org/vysper/bernd/... account specific... /content/jids/org/vysper/gerolf/... account specific... /content/jids/org/xmpp/gerolf/... account specific... Bernd --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
