[TYPO3-core] RFC: #15626: Feature: Add stdWrap to config.additionalHeaders

[JoH asenau]

>> I am also not sure if that is right. "config." is still a very valid
>> and not only historical entry point for "global configuration"
>> regarding the generation of a page. With "page.config" you can
>> overwrite certain behaviours on a typeNum scope.
>> 
>> The main issue with using stdWrap on these properties, is that there
>> isn't necessarily access to a valid cObj when certain properties are
>> being read, so usually you don't even have access to TypoScript.
>> Some of the setting even affect how "stdWrap" behaves (e.g.
>> "locale_all"). 
>> 
>> So it is right that the config.* top level array (and its
>> page.config.* brothers) are a place where "miscelaneous" settings
>> are made, but we can still have stdWrap in certain situations, and
>> this is one of it. In this case, additionalHeaders give out
>> HTTP-headers, which you cannot do with "page.headerData" level (you
>> can only "emulate" them). 
> 
> i totally agree here. config is a flat array which only uses plain
> strings for "configuration". I see no usecase where you need special
> handling with stdWrap and these strings, the only matter can be
> handled with simple conditions.

So do you agree or don't you? - As far as I understood, Ernesto wrote it would be OK to have stdWrap for certain (but not all) parameters of the config-Array, while you wrote just the contrary ;-)

Cheers

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your gob sometimes!)
Dieter Nuhr, German comedian
Xing: http://contact.cybercraft.de
Twitter: http://twitter.com/bunnyfield
TYPO3 cookbook (2nd edition): http://www.typo3experts.com