Re: From Component API to Sling API (was: Simplifying our component api)

2007-10-09 Thread Bertrand Delacretaz
On 10/9/07, David Nuescheler <[EMAIL PROTECTED]> wrote: > ...I think generally I would be cautious about introducing too much > abstraction. > > In many respects unnecessary abstraction causes software to fail in the > market. > I agree with Stefano 100% on this one ... Ok - I see your point, t

Re: From Component API to Sling API (was: Simplifying our component api)

2007-10-09 Thread David Nuescheler
Hi all, > Am Montag, den 08.10.2007, 12:08 +0200 schrieb Bertrand Delacretaz: > > Yes, so my proposal is not much different to what we have now, except > > that, as we see below, Content and Servlets are more decoupled from > > JCR, mostly by using URIs instead of paths. > > I like this (further)

Re: From Component API to Sling API (was: Simplifying our component api)

2007-10-08 Thread Felix Meschberger
Am Montag, den 08.10.2007, 12:08 +0200 schrieb Bertrand Delacretaz: > Yes, so my proposal is not much different to what we have now, except > that, as we see below, Content and Servlets are more decoupled from > JCR, mostly by using URIs instead of paths. I like this (further) decoupling. This is

Re: From Component API to Sling API (was: Simplifying our component api)

2007-10-08 Thread Bertrand Delacretaz
On 10/8/07, Felix Meschberger <[EMAIL PROTECTED]> wrote: > >... The ResourceResolver filter selects the Resource that the current > > request applies to. > > This is currently called the ContentResolver and a Resource is currently > called Content manifested by an implementation of the Content int

Re: From Component API to Sling API (was: Simplifying our component api)

2007-10-08 Thread Felix Meschberger
Am Montag, den 08.10.2007, 08:58 +0200 schrieb Bertrand Delacretaz: > I *think* the model below more or less matches the current resource > processing model, but makes it a bit more general and less dependent > on JCR. Making it more generic and more plainly REST-oriented might > help drive Sling a

Re: From Component API to Sling API (was: Simplifying our component api)

2007-10-07 Thread Bertrand Delacretaz
On 10/4/07, Felix Meschberger <[EMAIL PROTECTED]> wrote: > ...After the introduction of the topic by Carsten and some initial > discussion, I created issue SLING-28 [1] and committed a first > prototype. After having it around for some days now, I want to call for > a final discussion on this topi

From Component API to Sling API (was: Simplifying our component api)

2007-10-04 Thread Felix Meschberger
Hi all, After the introduction of the topic by Carsten and some initial discussion, I created issue SLING-28 [1] and committed a first prototype. After having it around for some days now, I want to call for a final discussion on this topic. Is there anything, which would go wrong in this directio