consider the following use case:
- an OSGi/Sling-based library provides a SPI interface
- applications of multiple tenants are deployed on the same instance
- each tenant uses a different content tree, e.g. /content/tenant1 and
/content/tenant2
- each tenant's application wants to register a diffe
Hi Stefan
this is definitely an interesting approach. I can see the potential, but
so far I haven't really seen use cases (which doesn't mean there are non).
If I understand correctly, you do the matching based on the path which
avoids the need of introducing an explicit concept of a tenant. On t
Hi,
On Tue, Sep 12, 2017 at 7:47 AM, Stefan Seifert wrote:
> ...do you have better ideas for configuring the mapping or the
> implementation?...
I don't know if it's a better idea but here are some thoughts.
In my upcoming adaptTo talk I'll mention making resource types
multi-tenant, by prefix
On Tuesday 12 September 2017 14:47:22 Stefan Seifert wrote:
> consider the following use case:
> - an OSGi/Sling-based library provides a SPI interface
> - applications of multiple tenants are deployed on the same instance
> - each tenant uses a different content tree, e.g. /content/tenant1 and
> /
>-Original Message-
>From: Carsten Ziegeler [mailto:cziege...@apache.org]
>Sent: Tuesday, September 12, 2017 7:41 PM
>To: dev@sling.apache.org; Stefan Seifert
>Subject: Re: [RT] Context-Aware Services - Multitenancy for SPI
>implementations
>If I understand
>-Original Message-
>From: Bertrand Delacretaz [mailto:bdelacre...@apache.org]
>Sent: Tuesday, September 12, 2017 8:31 PM
>To: dev
>Subject: Re: [RT] Context-Aware Services - Multitenancy for SPI
>implementations
>In my upcoming adaptTo talk I'll mention ma
