You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2023/04/13 05:02:00 UTC

[jira] [Resolved] (SLING-1630) Architecture of Sling

     [ https://issues.apache.org/jira/browse/SLING-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-1630.
-------------------------------------
    Resolution: Won't Fix

> Architecture of Sling
> ---------------------
>
>                 Key: SLING-1630
>                 URL: https://issues.apache.org/jira/browse/SLING-1630
>             Project: Sling
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Alison Heimoz
>            Priority: Minor
>
> - typos, some of which impact ease of understanding
> - OSGi
>   -- a sentence or two on why OSGi was chosen would be interesting
>     --- e.g. the advantages (contracts, dependencies, services are dynamic)
>     --- link to something like http://www.informit.com/articles/article.aspx?p=1565539&seqNum=2 ?
> - introductory list:
>   -- would move the "Resources" entry further up in the list as it is the "central mantra"; i.e. first or second - before it is 
>      referenced in any way
> ...tbc...



--
This message was sent by Atlassian Jira
(v8.20.10#820010)