Justin Edelson worte: > On 2/10/10 2:37 AM, Carsten Ziegeler wrote: >> Justin Edelson wrote: >>> Thanks for your feedback. What do you think about SessionConfigurer as >>> the interface name? >> I see the interface but I fail to see a use case for this :) >> I'm not against it, but just curious why this is needed. > > As I mentioned earlier, my specific use case is to register namespace > prefixes in the session-local registry. I suspect that other uses of > this SessionConfigurer function will arise in the future, but this is > the only one I have for now. Ah, ok, sorry I didn't saw that in a previous mail.
Now, I'm wondering if there is anything else except namespace prefixes? We already have support for the bundle header "Sling-Namespaces" which does exactly this: a bundle can define namespace prefixes in the header and each session gets exactly these prefixes set. (Unfortunately the code seems to be broken atm, see SLING-1366). So, if the header support would be sufficient for you, we woudn't need the SessionConfigurer :) Regards Carsten -- Carsten Ziegeler [email protected]
