You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Felix Meschberger <fm...@gmail.com> on 2007/10/16 09:02:10 UTC

[POLL] microsling: Future of microsling

Hi all,

After the introduction [1] of microsling as a simple testbed for the
discussions around a new Sling API [2] and some discussions on the list,
I want to poll the communities opionion on the following question:

        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 ?

Of course the discussion on the exact Sling API has not been finalized
yet, and microsling needs some polishing here and there. This is just
about the general question.

Thanks for any replies.

Regards
Felix


Re: [POLL] microsling: Future of microsling

Posted by Bertrand Delacretaz <bd...@apache.org>.
On 10/16/07, Felix Meschberger <fm...@gmail.com> 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

Re: [POLL] microsling: Future of microsling

Posted by David Nuescheler <da...@day.com>.
>         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 ?
+1

... loving it ;)

regards,
david