Fabien Potencier Sensio CEO - symfony lead developer sensiolabs.com | symfony-project.com | aide-de-camp.org Tél: +33 1 40 99 80 80
Nicolas Perriault wrote: > On Mon, Mar 3, 2008 at 1:25 PM, Rytis Daugirdas > <[EMAIL PROTECTED]> wrote: > >> For example, routing.yml becomes a monster for a bigger app and >> depending on the user type logged in, some of the rules can never be >> used by that user type. > > You can split routing yaml files and include them using php in the the > main routing.yml, eg. : > > <?php include dirname(__FILE__).'/routing.blog.php'; ?> > <?php include dirname(__FILE__).'/routing.forum.php'; ?> > <?php include dirname(__FILE__).'/routing.cms.php'; ?> > > Okay, weird black magic here ^__^ > >> Getting the logged in user (in an Action) would return a >> different type of user depending on who's logged in (weird). > > Credentials are designed for this, no? Maybe I didn't get your point. > >> I would certainly prefer multiple apps since conceptually it's "the >> right thing to do", but I'm not sure if I'm not going to run into >> problems/annoyances later. > > In 1.0 you'll encounter some severe issues, such as separates routing > config access due to singleton use... Problematic when you want to > make a preview link from your back office :/ > > This issue is solved in 1.1. This issue is not solved yet. All changes are done to make this happens but it still needs some work. > > So I would promote the single app approach if you start with 1.0, and > multiple apps if you go with 1.1. > > ++ > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
