Hi Wow, V2.0 already :-)
We seem to agree on the need to merge µsling back into Sling, so I think it' be good to agree on the goals first - feel free to comment and expand on the following list of high-level goals and requirements for µsling 2.0. µsling 2.0 is a preconfigured instance of Sling, meant to allow web developers to test drive Sling by building scripted web and REST applications backed by a JCR repository. The µsling 2.0 distribution only requires a Java 5 VM to run, no installation is needed. Fifteen minutes should be enough to start µsling and understand the basic concepts, based on self-guiding examples. Java programming is not required to build web and REST applications with µsling 2.0: both server-side and client-side javascript code and presentation templates can be used to process HTTP requests. Other scripting and templating languages (JSP and BSF-supported ones) can be plugged in easily. The µjax "application protocol" and client-side javascript "JCR proxy" library make it easy to write powerful Ajaxish JCR-based applications with µsling 2.0. µsling 2.0 is built on the same codebase as Sling, it's only a specific configuration of Sling. All µsling 2.0 features are available in Sling applications, as long as they are enabled in the Sling configuration. Sling (and µsling, as it runs the same core code) uses OSGi to modularize the framework, but µsling does not require any OSGI skills, and makes OSGI largely invisible to beginners. All Sling features and modules can also be activated in a µsling 2.0 instance, by installing and activating the required OSGi bundles. µsling 2.0 passes all the integration tests of the existing microsling test suite (SVN revision 605206), with minor adaptations where needed. µsling 2.0 includes a WebDAV server module to make it easy to copy scripts into the JCR repository. This WebDAV module currently supports the Jackrabbit JCR repository, but Sling is meant to run with any JCR repository. -Bertrand
