Am 12.01.15 um 10:44 schrieb Felix Meschberger:
> Hi all
> 
> Carsten started to review the Sightly Engine API in SLING-4275 [1]. Since 
> this issue covers 4 topics, I think it would be best to quickly discuss these 
> topic in separate threads.
> 
> #5 ResourceResolution helper
> 
> The ResourceResolution helper kind of duplicates and/or extends functionality 
> attributable to Script and Servlet Resolution.
> 
> The question is whether we want to move this API to the Sling API at the 
> expense of increasing the respective API package version and thus requiring 
> an update to other bundles just to cope with this extended methods …
> 
> (This actually blends into another discussion we should be having on the 
> evolution of the Sling API itself: Whenever we update something in the Sling 
> API, it has a potential dramatic ripple-down effect to other bundles. Lets 
> not discuss this here and now, though)
> 
If this API is of general (scripting) use, we should put it into a
common place; if it's just for scripting we have the scripting api; if
it's more general, I think Sling API is the place.


Carsten
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Reply via email to