You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by paksegu <pa...@yahoo.com> on 2008/01/10 00:05:02 UTC
JackRabbit -Server vs JackRabbit-Rmi
Hi
I have a vague idea on this 2 components but to help increase my understanding what are the difference between this 2 components (JackRabbit -Server vs JackRabbit-Rmi), what are the benefits of using one over the other and in what particular usecases would you use jcr-server over jcr-rmi, looking at the code that jcr-rmi contain jcr-server? and in the case of sling which one is being used? Thanks
Ransford Segu-Baffoe
paksegu@yahoo.com
https://serenade.dev.java.net/
http://www.noqturnalmediasystems.com/
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
Re: JackRabbit -Server vs JackRabbit-Rmi
Posted by paksegu <pa...@yahoo.com>.
Thanks for the feedback indeed helpful, I wanted to clarify my thoughts. Thanks
Jukka Zitting <ju...@gmail.com> wrote: Hi,
On Jan 10, 2008 1:05 AM, paksegu
wrote:
> I have a vague idea on this 2 components but to help increase my understanding
> what are the difference between this 2 components (JackRabbit -Server vs
> JackRabbit-Rmi), what are the benefits of using one over the other and in what
> particular usecases would you use jcr-server over jcr-rmi, looking at the code
> that jcr-rmi contain jcr-server?
If you haven't seen them already, see the jackrabbit-jcr-server and
jackrabbit-jcr-rmi pages on the Jackrabbit web site ([1] and [2]) for
more details about these components. To summarize:
The jackrabbit-jcr-server component contains code that makes a JCR
repository accessible using the WebDAV protocol. With
jackrabbit-jcr-server you'd use a WebDAV client to work with the
repository. The Jackrabbit sandbox contains a WebDAV-based JCR
remoting component but that's not yet ready for production use.
The jackrabbit-jcr-rmi component contains code that makes a JCR
repository remotely accessible using RMI. With jackrabbit-jcr-rmi
you'd use the standard JCR API to work with the repository. The
jackrabbit-jcr-rmi component is stable and well-tested, but not
suitable for performance-critical applications.
[1] http://jackrabbit.apache.org/doc/components/jcr-server.html
[2] http://jackrabbit.apache.org/doc/components/jcr-rmi.html
BR,
JUkka Zitting
Ransford Segu-Baffoe
paksegu@yahoo.com
https://serenade.dev.java.net/
http://www.noqturnalmediasystems.com/
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
Re: JackRabbit -Server vs JackRabbit-Rmi
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Jan 10, 2008 1:05 AM, paksegu <pa...@yahoo.com> wrote:
> I have a vague idea on this 2 components but to help increase my understanding
> what are the difference between this 2 components (JackRabbit -Server vs
> JackRabbit-Rmi), what are the benefits of using one over the other and in what
> particular usecases would you use jcr-server over jcr-rmi, looking at the code
> that jcr-rmi contain jcr-server?
If you haven't seen them already, see the jackrabbit-jcr-server and
jackrabbit-jcr-rmi pages on the Jackrabbit web site ([1] and [2]) for
more details about these components. To summarize:
The jackrabbit-jcr-server component contains code that makes a JCR
repository accessible using the WebDAV protocol. With
jackrabbit-jcr-server you'd use a WebDAV client to work with the
repository. The Jackrabbit sandbox contains a WebDAV-based JCR
remoting component but that's not yet ready for production use.
The jackrabbit-jcr-rmi component contains code that makes a JCR
repository remotely accessible using RMI. With jackrabbit-jcr-rmi
you'd use the standard JCR API to work with the repository. The
jackrabbit-jcr-rmi component is stable and well-tested, but not
suitable for performance-critical applications.
[1] http://jackrabbit.apache.org/doc/components/jcr-server.html
[2] http://jackrabbit.apache.org/doc/components/jcr-rmi.html
BR,
JUkka Zitting