[TYPO3-mvc] access control & localization: are they killing the idea of extbase by now?

Sebastian Kurfürst sebastian at typo3.org
Wed Jan 6 15:49:47 CET 2010


Hey,

> Well, implementing Access Control via AOP is beautiful - but no AOP no
> Access Control doesn't convince me ;-) Sadly you are right, there is not
> to much access control stuff in pibase - atm I can only think of the
> typical cObj->enableFields() for generating additional stuff for your
> where-clauses. But I think it might be a good idea to put something like
> this and perhaps a bit more in Extbase.
I'll be happy to discuss any API somebody comes up with :-)

> It partly works, see http://forge.typo3.org/issues/show/4639
> quote: "Localization works read-only by now. We need to implement a
> reverse overlay."
Thanks1

> For me the key question is, does it make sense to use "extbase" the
> other way too. By creating very basic v4 compatible localization and
> access control features in extbase now, most of the extbase-based
> extension would use the same api. If v5 comes in we would find a way to
> develop the same api there with an v5-"extbase" package. What do you and
> especially Jochen think about this?
I think while it is generally possible, to me it sounds like very much
work for the last 5% - so for only a marginal gain. I guess I wouldn't
work on that, but if somebody wants to try, why not? :)

Greets,
Sebastian


More information about the TYPO3-project-typo3v4mvc mailing list