+1 for creating a "simple" FS resource provider with _pluggable_
formats. Maybe it doesn't even need to be FS specific? Just "simple"
:)
Things like a mock JCR implementation are very useful for some
use-cases, but IMHO they could also be achieved with a custom adapter
factory and thus be highly
+1 on a simple resource provider, I'm curious about the focus on a filesystem
provider. I've started playing around with creating one and I see a clear
logical association between what a resource provider needs and a key-value
store. Good key-value stores already have versioning, and non
Am 12.11.2018 um 14:31 schrieb Bertrand Delacretaz:
Hi,
On Mon, Nov 12, 2018 at 12:20 PM Carsten Ziegeler wrote:
...As a side note, the markdown resource provider in the whiteboard is
another file system based rp which is closer to my use case, except that
it supports markdown files
Hi,
On Mon, Nov 12, 2018 at 12:20 PM Carsten Ziegeler wrote:
> ...As a side note, the markdown resource provider in the whiteboard is
> another file system based rp which is closer to my use case, except that
> it supports markdown files instead of json...
Having a GitHub-friendly resource
; Stefan Seifert
Subject: Re: [RT] Simple File System Resource Provider
It's only 1 - 2 from your list is taking a structured json and creates
resources out of the structure (if I'm not mistaken) which is something
I don't need.
With the approach I hope there is no need for b) (caching
egeler [mailto:cziege...@apache.org]
>Sent: Monday, November 12, 2018 11:51 AM
>To: dev@sling.apache.org; Stefan Seifert
>Subject: Re: [RT] Simple File System Resource Provider
>
>It's only 1 - 2 from your list is taking a structured json and creates
>resources out of the struct
: Carsten Ziegeler [mailto:cziege...@apache.org]
Sent: Monday, November 12, 2018 11:20 AM
To: dev@sling.apache.org; Stefan Seifert
Subject: Re: [RT] Simple File System Resource Provider
Hi,
I would be totally happy if we can factor out the extensions, I'm
wondering however if this is worth the effort
11:20 AM
>To: dev@sling.apache.org; Stefan Seifert
>Subject: Re: [RT] Simple File System Resource Provider
>
>Hi,
>
>I would be totally happy if we can factor out the extensions, I'm
>wondering however if this is worth the effort.
>
>In my use case, I would like to have a simp
Hi,
I would be totally happy if we can factor out the extensions, I'm
wondering however if this is worth the effort.
In my use case, I would like to have a simple mapping to directories and
files, supporting json and binary files. So a resource maps to a json
file 1:1 regardless of the
yes, the current implementation of the fsresource provider is no longer any
simple.
it currently supports three (configurable) modes:
1. simple mapping of folders and binary files from filesystem (this was the
starting point of fsresource)
2. reading structured resource data from JSON files and
Seeing as the current filesystem resource provider does need an update to java
8 api, it would be nice to refactor / start over with that one and make it more
generic / extensible? It has some caveats (like the start up scanning etc.)
that would be nice to have fixed in a more elegant way.
Roy
11 matches
Mail list logo
