On 27 Jun., 20:20, Fabien POTENCIER <[EMAIL PROTECTED]> wrote: > Hi all, > > As I currently do some major changes, I want to give you some more > information on what's going on in the trunk. > > One of main "problem" with the current symfony 1.0 design is the use of > a lot of singleton objects and static classes/methods. It limits the > ability to override those classes or to change the behavior of certain > parts of the framework (sfRouting, sfI18N, sfContext for example).
Another main problem is the missing decoupling of key features like action instantiation, validation, action execution and action rendering. Currently this all happens within sfController::forward() and sfExecutionFilter. That makes it really hard to write an own sfController driver, e.g. a page controller. I believe in the process of refactoring the view layer it's the right time to also take this into account. I could imagine appropriate context objects to manage these things. One advantage of my "factory config change suggestion" is that we could use factories.yml to configure arbitrary context objects as the actual instantiation would simply happen in the factory() method taking only a parameters array as argument. Oh.. some more name ideas for the "factory method": instantiate() or make() or makeInstance() ...but i think factory() is better and clearer. Regards, Matthias --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
