[TYPO3-mvc] Concept of dynamic USER_INT switch maybe has to be refactored?

[Steffen Ritter]

Franz Koch schrieb:
> Hi Jochen,
> 
>> Using the new convertToUserIntObject() will not work as the the
>> Dispatcher must be called as USER od USER_INT. If it is already defined
>> to be USER the method convertToUserIntObject() inside the Extension will
>> never be called.
> 
> Why not? You can trigger convertToUserIntObject() from inside your 
> extension (in this case the dispatcher) and immediately return NULL. 
> Typo3 will then check if convertToUserIntObject was triggered and recall 
> the extension as USER_INT (with a slight processing overhead of course).
> The check for USER_INT or not would have to be done in the dispatcher 
> right after the initialization of the request object - thus as early as 
> possible.
> 
> Do you really think this won't work that way?
> 
if the dispatcher is userobject, and is cached it would not get called 
anymore so that it may trigger i think.