[TYPO3-ect] Final goal of the new framework ?

[Jean-Baptiste Rio]

Hi list,

I'm following all the threads in this list, and i'm a lot disturbed. I 
try to see how the new framework will find its place in the Typo3 galaxy.

I see two ways :
- It aims to be an alternate way to build extension
- It aims to be the new standard for extensions

The first way seems to me ok... I would say, why not... :)
The second way frightens me. I agree that's sometimes it's easier to 
build new concepts instead of reusing the old ones. But i also think to 
my bunch of extensions, and i wonder myself if i will have to rebuild 
all of them, first of all to make my sites work with the next version of 
Typo3 (4.5, 5.0, ...) and secondly to enrich the community extensions 
with my work.

I agree that some improvements have to be made in the current extension 
concept but, when i look at the tons of extensions in the TER, this 
concept seems to work and to be easy to understand for Typo3 community 
(thanks, also, to the kickstarter team :)). Ok, not all extensions are 
correct nor interesting. But not all extension are in the TER too.

I'm not against the new framework concept, i'm just wondering if you 
have thought to all consequences in terms of works, backwards 
compatibility, product stability, etc... if you decide to make it the 
only one for extensions or if you decide to change the structure of 
extensions (see "Zend style extensions scheme").

Last but not least, i've seen that SOAP integration is planned for Typo3
5.0 (roadmap). Why not build the new extension concept as Typo3 Web 
Services ? It will have many advantages without the disadvantages of the 
extension manager rewriting.

Regards,

JB