Concepts and Ideas
These pages contain concepts and ideas under development for future inclusion in Sling.
Taking the JCR Paradigm Everything is Content to Sling (IMPLEMENTED)
We should define the SlingException as a RuntimeException and use it as the base class for all exceptions defined in the Sling API. (IMPLEMENTED)
Version Number and Release Planning Concept (IMPLEMENTED)
Easier and more flexible access to ResourceResolver instances providing the ResourceResolverFactory interface in the Sling API and allow for the extensibility of the factory using new ResourceResolverProvider services. (IMPLEMENTED)
Extend resource resolution with an integrated and flexible mechanism (IMPLEMENTED)
How we could get the Sling Launcher to be updated through management interfaces such as the Felix Web Console or the Felix Shell. (IMPLEMENTED)
With support for virtual host resolution we made a first step towards multitenancy support. I would like to propose a further step to provide a basis for further multitenancy support throughout Sling.
How to generalize initiation of the authentication process. (IMPLEMENTED)
Further enhancements to the Flexible Resource Resolution (DRAFT)
(NO FURTHER WORK DONE)
Separating authentication from ResourceResolver access (ammending Add ResourceResolverFactory Service Interface) (NOT IMPLEMENTED)
Introduce new service level authentication to replace loginAdministrative (PROTOTYPE)
Define a mechanism to allow an Authentication Handler to validate the user's identity and signal that to the ResourceResolverFactory in the authentication information.(DRAFT)
Definition of a ResourceProvider infrastructure to enable supporting HTTP proxy functionality for Sling (DRAFT)
Describes different scenarios and use cases from the real world that the Sling Tenant implementing is supposed to fulfill.
OUTDATED - Sling has moved to Git
Status: Implemented, 2017-10-12
STATUS: implemented as of 2017-11-15