RMI based ResourceProvider

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

RMI based ResourceProvider

Jason E Bailey-2
I don't have any legitimate use case for this, I just like to see if I
can make things work in a certain way.
I was thinking, wouldn't it be cool if I had a ResourceProvider which
was a connected via RMI to a JCR Resource Provider for a specific path.
I could then have one instance dedicated to being the source of record
for content, but the processing of this content, indexing, generating
pages, etc.  Would be on the individual servers.
Would appreciate feedback from anyone whose done this.

- Jason


Reply | Threaded
Open this post in threaded view
|

Re: RMI based ResourceProvider

Bertrand Delacretaz
Hi Jason,

On Wed, Jun 27, 2018 at 11:57 PM Jason E Bailey <[hidden email]> wrote:
> ...I was thinking, wouldn't it be cool if I had a ResourceProvider which
> was a connected via RMI to a JCR Resource Provider for a specific path...

I'm not sure if Oak still provides an RMI interface, but Jackrabbit did.

In general, the problem with RMI access to JCR is that it's very
chatty due to the low granularity of JCR, which can hinder
performance.

I've been thinking for a while that a remote ResourceProvider that
aggregates Resources in larger chunks might be useful, using
micro-trees that can represent a website page for example, based on
the properties and resource types that define the micro-tree
boundaries. In this way you'd reduce the granularity to improve
performance.

That's probably much more complicated than what you are after though,
just wanted to mention it as food for thought.

-Bertrand
Reply | Threaded
Open this post in threaded view
|

Re: RMI based ResourceProvider

Jason E Bailey-2
I understand what you're saying, it would be problematic to execute an RMI call for every request of a property :(  you're talking the same type of batching that the filevault uses. I could implement a custom ResourceProvider to do this but not all ResourceProviders are equal and it would be great to do this via a JCR implementation.



- Jason

On Thu, Jun 28, 2018, at 5:18 AM, Bertrand Delacretaz wrote:

> Hi Jason,
>
> On Wed, Jun 27, 2018 at 11:57 PM Jason E Bailey <[hidden email]> wrote:
> > ...I was thinking, wouldn't it be cool if I had a ResourceProvider which
> > was a connected via RMI to a JCR Resource Provider for a specific path...
>
> I'm not sure if Oak still provides an RMI interface, but Jackrabbit did.
>
> In general, the problem with RMI access to JCR is that it's very
> chatty due to the low granularity of JCR, which can hinder
> performance.
>
> I've been thinking for a while that a remote ResourceProvider that
> aggregates Resources in larger chunks might be useful, using
> micro-trees that can represent a website page for example, based on
> the properties and resource types that define the micro-tree
> boundaries. In this way you'd reduce the granularity to improve
> performance.
>
> That's probably much more complicated than what you are after though,
> just wanted to mention it as food for thought.
>
> -Bertrand