[
https://issues.apache.org/jira/browse/SLING-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609893#comment-17609893
]
Bertrand Delacretaz commented on SLING-47:
------------------------------------------
I'll be mentioning that today in a discussion on the history of Sling - for the
curious among you, the code is now archived at
https://svn.apache.org/repos/asf/sling/whiteboard/microsling/
> microsling - simple webapp to demonstrate the core principles of Sling
> ----------------------------------------------------------------------
>
> Key: SLING-47
> URL: https://issues.apache.org/jira/browse/SLING-47
> Project: Sling
> Issue Type: New Feature
> Components: Engine
> Reporter: Bertrand Delacretaz
> Priority: Minor
> Attachments: microsling-homepage.html, microsling-homepage.html
>
>
> Following our recent API redesign discussions (see
> http://cwiki.apache.org/confluence/display/SLING/Sling+API+Redesign in
> particular), I have started working on "microsling", a webapp that
> demonstrates my understanding of the "most important parts" of Sling.
> The goal is to create very simple codebase that helps in understanding how
> Sling processes HTTP requests: the current Sling codebase contains many
> (useful) things which are not central to Sling's vision, and make it hard to
> understand what Sling is really about.
> The first version that I'm going to commit to
> http://svn.apache.org/repos/asf/incubator/sling/whiteboard/microsling is
> probably not worth looking at in detail, I hope to have a "good enough for
> review" version in a few days.
> Note that I have not studied Sling's internals in detail - I'm starting from
> scratch based on my current understanding of how things work. The goal is not
> to replace any of the Sling's current code, but having a very simple thing to
> play with will hopefully help us in our simplification efforts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
