Hi David,

just having backward compatibility and potential further evolution in mind.
Would it make sense for regions to follow some namespace concept an reserve
a certain namespace. So even if the future brings new scenarios where we
might need new reserved regions we could have some "system" namespace or
so. Additionally it is easier to layer different "owners" on top and
explicitly declare the ownership (e.g. vendor customer scenario where we
would want to check weather customers hook into regions that are supposed
to be internal).

Cheers
Dominik

Cheers
Dominik

On Fri, Jul 13, 2018 at 12:20 PM David Bosschaert <
[email protected]> wrote:

> Hi Bertrand,
>
> On Fri, 13 Jul 2018 at 12:08, Bertrand Delacretaz <[email protected]>
> wrote:
>
> > Hi David,
> >
> > On Fri, Jul 13, 2018 at 11:54 AM David Bosschaert
> > <[email protected]> wrote:
> > > ...Yes, 'global' is the magic name for the region available to
> everyone.
> > This
> > > includes bundles that are in different regions or bundles that are in
> no
> > > region at all....
> >
> > Ok, so IIUC "global" is the only reserved region name, and other names
> > can be selected freely?
> >
>
> Yep, it's defined as a constant at [2]. All other names can be selected at
> will.
>
>
> > If I'm correct it might be good to mention that at [1], for clarity.
> >
>
> Good point - I've updated [1] for this.
>
> Also (while I'm in nitpicking mode ;-) how about using "API Controller
> > and API Regions" as the title of that document? It speaks more about
> > regions than about the controller itself.
> >
>
> Also good point - I've changed this too (I didn't change the file name as I
> didn't want to break any links).
>
> Best regards,
>
> David
>
>
> > Thanks for this, it looks quite useful!
> >
> > -Bertrand
> >
> > [1]
> >
> https://github.com/apache/sling-org-apache-sling-feature/blob/master/apicontroller.md
>
>
> [2]
>
> https://github.com/apache/sling-whiteboard/blob/master/featuremodel/feature-whitelist/src/main/java/org/apache/sling/feature/whitelist/WhitelistService.java#L24
>

Reply via email to