[sling-whiteboard] branch master updated: Update api controller proposal

[cz...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

cziegeler pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-whiteboard.git


The following commit(s) were added to refs/heads/master by this push:
     new 6d32bb5  Update api controller proposal
6d32bb5 is described below

commit 6d32bb59567ab6fa9edbfe9081d4bddd6c8ddf20
Author: Carsten Ziegeler <cz...@apache.org>
AuthorDate: Mon Nov 6 15:38:54 2017 +0100

    Update api controller proposal
---
 featuremodel/apicontroller.md | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/featuremodel/apicontroller.md b/featuremodel/apicontroller.md
index 949d8a3..32f3e6e 100644
--- a/featuremodel/apicontroller.md
+++ b/featuremodel/apicontroller.md
@@ -1,6 +1,6 @@
 # API Controller
 
-If you're assembling an application out of several features and provide this application as a platform for customers to extend, an additional control of the API provided by the platform is needed. The bundles within the features provide all kinds of APIs but you might not want to expose all of these as extension points but rather want to use some of it internally within your features.
+If you're assembling a platform (in contrast to a final application) out of several features and provide this platform for customers to build their application on top if, an additional control of the API provided by the platform is needed. The bundles within the features provide all kinds of APIs but you might not want to expose all of these as extension points but rather want to use some of it internally within either a single feature or share within your features.
 
 This is a proposal about how to add such additional metadata to the feature model. An API controller at runtime enforces the rules.
 
@@ -9,20 +9,20 @@ This is a proposal about how to add such additional metadata to the feature mode
 A feature exports some api, however there are different types of clients of the API:
 
 * Bundles shipped as part of the platform
-* 3rd party bundles based on the platform
+* Application bundles using the platform
 
-We can generalize this by saying that API is either globally visible (to every client) or only visible to features within the same context. Usually this is referred to as a "region": The platform spawns its own region and a customer application has its own region, too. In theory there could be several customer applications running in the same framework, and each application has its own region.
+We can generalize this by saying that API is either globally visible (to every client) or only visible to features within the same context. Usually this is referred to as a "region": The platform spawns its own region and a customer application has its own region, too. In theory there could be several customer applications running in the same framework on top of the platform, and each application has its own region.
 
 Without any further information, API is globally visible by default. However, for platform features we want the opposite as we want to ensure that newly added API is not world-wide visible by default. Therefore we'll add an additional build time check (analyzer) that checks that each platform feature has an api controller configuration as below.
 
-A feature can have an additional extension JSON named exports:
+A feature can have an additional extension JSON named regions:
 
-    "exports" : {
+    "regions" : {
         "region" : "platform" // name of the region,
-        "global" : [
+        "global-exports" : [
             "org.apache.sling.resource.api.*"
         ],
-        "local" : [
+        "region-exports" : [
             "org.apache.sling.commons.scheduler"
         ]
     }
@@ -35,9 +35,9 @@ In the example above the feature declares:
 
 Of course the above mentioned packages need to be exported by some bundle within the feature.
 
-If the exports extension is missing, it is assumed that all packages are exported and that the feature runs in the global region.
+If the regions extension is missing, it is assumed that all packages are exported and that the feature runs in the global region.
 
-If the region information is missing, the global region is used. If the packages list for global or local is missing, it is assumed to be all packages. If none should be exported, an empty array needs to be specified.
+If the region information is missing, the global region is used. If the packages list for global-exports or local-exports is missing, it is assumed to be all packages. If none should be exported, an empty array needs to be specified.
 
 This model is intentionally kept simple and restricted to a feature being in only a single region. In theory we could think of use cases where a feature is shared across two (or more) regions, but not shared globally. However this gets pretty complicated easily and therefore we suggest to make such features global.
 

-- 
To stop receiving notification emails like this one, please contact
['"commits@sling.apache.org" <co...@sling.apache.org>'].