Hi, On Wed, Apr 2, 2008 at 1:10 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > Bertrand Delacretaz wrote: > > ...I suggest moving that path to /bundles/sling/sling.js, where /bundles > > makes it clear that this resource comes from a bundle....
> ... Hmm, I'm not sure :) - I think it shouldn't be of interest for the client > to know where the js comes from (bundle vs repository).... It can be of interesting for people who wonder where that file comes from, as most of the other requests can be traced to repository nodes. Not sure if /bundles is a good choice, but having a path convention for things that (by default) are served from bundles would help people find out what is what. Maybe /static/sling-client/sling.js ? > ... Furthermore I think we should move the js to a different bundle... Agree with that, sling-client maybe? That could also contain the test page that is currently under launchpad/content. -Bertrand
