[TYPO3-team-core-v5] Getting rid of index_dev.php - please give feedback

[Karsten Dambekalns]

Hi Bastian.

On 26.02.2009 10:43 Uhr, Bastian Waidelich wrote:
> I can't really think of the best way for such meta data. It might be
> some cookie, request headers or a different (sub-)domain..
 >
> What is a common scenario for a change of context anyways? Does it make
> sense to share one Public/index.php for multiple contexts on a live server?

Most probably development (I run my code in dev context most of the 
time) or (in the future) some debugging scenarios (enable debugging 
output on a server) come to my mind.

For development any way of switching should be possible, if needed at 
all[1]. I am happy for now with a simple SetEnv line in my .htaccess file.

Live switching is always related to permission issues, after all you 
want to protect your data potentially coming out through an exception. 
Until now simply deleting index_dev.php was a safe measure, so... any 
way that uses cookies or whatever seems to open potential holes.

Huh, so many open issues, so little time...


[1] Today I did a little benchmark to measure the effect of router 
caching, and as a side effect it turned out there is practically no 
speed difference between dev and production context.

Regards,
Karsten