On Mon, Nov 10, 2008 at 9:27 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> ...I find it troubling that Sling is reinventing JCR. This looks like a > symptom that JCR is not optimal for the things Sling wants to do. From > an architectural perspective I'd rather focus on improving JCR than > layering extra levels of abstraction on top of it.... I tend to agree, and IIUC the various comments in this thread, being able to mount additional resources (files, rss feeds, you name it), at least read-only, at the JCR level, would help a lot. But we don't have this today. Having to use both the Resource and JCR interfacts in Sling might not be optimal, but it allows us to do more than if we were to use just JCR. With this in mind, I agree with Felix and Carsten about the proposed changes, but I think we must be very careful to not bloat the extra layers of Sling. The proposed changes do improve the current situation, without adding complexity or new layers, IMHO, so I'm +1 on them. -Bertrand
