On 10/16/07, Felix Meschberger <[EMAIL PROTECTED]> wrote: > ... What do you think of (1) making microsling the "reference > implementation" of the new Sling API and thus (2) promoting it > to the trunk and finally (3) try to reuse parts of microsling > code for the real Sling ?...
Big +1 on all of this! Done right (it's not there yet, but progressing quickly), microsling can be quite useful for simple apps or environments. And if we take care of keeping it very small and understandable, it's a perfect introduction to the real Sling, for people who need that. We'll have to find a name for the real Sling though, maybe "Sling OSGi" is the most obvious? About (3), I think it's important that both Slings use the same API (for the main abstractions: Resource, SlingServlet, ResourceResolver, etc.): this will force us into a clean design for this API. -Bertrand
