I think you missunderstood me, or we're maybe talking about different things - as repeatedly stated we don't need to change the resource resolver - we have everything in place; and now we exactly need to define the use cases to know how the flags api should look like and which possibilites it has. The implementation of that api can do all kinds of stuff like using thread locals to access the current request etc.
Carsten 2013/12/13 Alexander Klimetschek <[email protected]> > On 11.12.2013, at 19:10, Carsten Ziegeler <[email protected]> wrote: > > > I think we're pretty clear now how we could implement this, basically > > everything is in place, so the resource resolver has all features we need > > in the way we need them. And we should now start defining the feature > flags > > api. > > Did you read my post? ;) I don't see the open question on how dynamic > those flags get into the resource resolver being answered, at least not > here. > > I think it really makes sense to experiment with that in an existing > service interface, let applications be written with that, and figure out > what the use cases are, before bending the resource resolver in any > direction. > > Cheers, > Alex > -- Carsten Ziegeler [email protected]
