I can see where you are going with this, however, in my mind there is
one key piece of functionality that Nodes do not provide which is the
adaptTo method. The adaptTo method would allow a resource to be
implemented and respond to many different Node types. I guess,
however, that this adaptable interface could be built into the OCM
layer? I re-read your post linked below, could you go into more detail
on your proposal?
-paddy
On Jan 2, 2008, at 1:39 AM, Jukka Zitting wrote:
Hi,
On Dec 29, 2007 9:51 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
After the recent thread on scripting "everything" and some off-line
discussions around this matter, I come to the conclusion, that it is
about time to introduce the Sling Paradigm:
Everything is a Resource
If Sling would be enhanced to make the ResourceResolver more flexibel
and powerful by the addition of ResourceProvider instances to
define a
virtual resource tree accessible (and iterable) through the
ResourceResolver, we can make Sling much more scriptable than it is
today.
Re-raising my earlier concern: "To me it seems like the Resource
interface, as currently envisioned, might well end up growing to a
mini-Node abstraction by time." [1]
Along those lines, my counter-proposal would be to use special
sling:servlet and sling:filter nodes for configuring and accessing
such resources, sticking with the "Everything is Content" paradigm.
:-)
[1] http://markmail.org/message/nmpzkpqtznd5cosv
BR,
Jukka Zitting
