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.
besides roster management, what else do we have to persist wrt:
-RFC3920
-RFC3921
-any important XEPs with "high" priority
?
Gerolf
On Wed, Apr 16, 2008 at 9:09 AM, Bernd Fondermann <
[EMAIL PROTECTED]> wrote:
> On Wed, Apr 16, 2008 at 9:01 AM, Gerolf Seitz <[EMAIL PROTECTED]>
> wrote:
> > personally, i don't have experience with JCR, but two fellow wicket
> > committers
> > will be releasing a wrapper for the JCR API soon (around May 1st),
> > basically to get rid of all the checked exceptions, but also with other
> nice
> > features :)
> > so maybe this would be an option...
> >
> > Gerolf
>
> we should at least try JCR.
>
> Maybe discuss first the general structure of the repository (nodes and
> stuff). How should we put eveything in place?
>
> I will now refresh my JCR memory so I can reply soundly to any ideas
> brought up here :-)
>
> Bernd
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
