Hi, Am Donnerstag, den 03.04.2008, 08:39 +0200 schrieb Bertrand Delacretaz: > On Wed, Apr 2, 2008 at 7:34 PM, Tobias Bocanegra > <[EMAIL PROTECTED]> wrote: > > what about putting the sling console to some other place? eg: > > > > /slingconsole > > /system/sling/console ? > > Agreed, but maybe /system/console to make it a bit shorter?
Actually a good idea ;-) The original path /sling stems from the times where did not yet have a good clue of how to place things.. > > > > > we should avoid 'cluttering' the root context as much as possible. > > furthermore, i wold move the sling.js to /libs/sling/docroot/sling.js > > Note that sling.js is served directly from its bundle, not from the > repository. I'd suggest /system/libs/sling.js, so that only the > /system root path is reserved for stuff provided by > Catapult^H^H^H^H^H^H^H Sling. I agree completely that we should put it into /system instead of /libs. But we should try to consolidate a bit. We have - besides the standard servlets in a relative path, the following absolute paths (taking Bertrands proposals into account): * /system/console - the sling console * /system/libs/sling.js - the client side library * /system/sling/info - the sling info servlet Now, this is a bit scattered. Given that the console and info are both servlets, we should place them in the same location. I would also not do the "libs" path in /system but trying to signal that sling.js actually is a static, we could do * /system/sling/console - the sling console * /system/sling/info - the info servlet * /system/sling/docroot/sling.js - the client side library WDYT ? Regards Felix BTW: Whether it is served directly from the bundle or from the repository is IMHO secondary and of no big importance to the casual user. > > -Bertrand
