On Dec 10, 2007 10:23 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Am Freitag, den 07.12.2007, 05:02 -0800 schrieb Bertrand Delacretaz
> > One interesting feature would to use an additional search path that depends 
> > on the beginning of the resource path, for example for a resource found at
> >   /content/blog/a/b/c
> > we'd look for scripts under
> >   /apps/blog...

> ...The questions are :
>
> * Is this just interesting or do we have a use case ?

See my upcoming "chickens, eggs and stars" post, there are several
interrelated issues here.

>
> * What happens if you move the resource to, say, /content/quark/a/b/c ?

That would break the link between content and scripts, of course.

>
> * Who defines what the "beginning of the resource path" is ?

currently in the /apps/XX path, XX is the second level of the resource
path, see ScriptSearchPathsBuilder

> ...At the moment I am rather sceptical, whether this is actually a good
> idea :-)...

I understand, I'll explain more shortly.

-Bertrand

Reply via email to