On Thu, Apr 3, 2008 at 9:57 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ... (with the exception regarding the "static" path, we can really place > that at /system/sling.js)... Agree with that, or docroot with mapping to /sling.js, I'm ok with both. > >... All this needs to be discoverable, so I'd make sure /system returns an > > HTML document with links to the above items. > > Not sure ;-) But adding such a thing does certainly not hurt.... My larger concern is that those resources, served by bundles, are not discoverable. What I love when working with a JCR repository (like on a unixish system) is that everything is very visible and hackable, in files and folders - and we lose this for those "magic" resources served by bundles. We don't need to address this right now, but as David mentions in this thread there should be a way to "see" those bundle resources along with what's stored in the repository. For now (or soon after our first release), making sure that all resources served by bundles are under /system might be a good idea, if we want to make that a virtual path later, that is visible (but read-only) in the repository - like the /proc filesystem on linux. -Bertrand
