[EMAIL PROTECTED] wrote: > I think having multiple applications in one project is a good idea, > and if main drawbacks of this design are dismissed (for ex links > between apps :) ) I see no reasons not to keep applications. > > If you have a very large project, it helps developers to work on a > portion without interfering with others, simplify routing, credentials > management, etc. > > Nautile > > On 28 juin, 05:46, Stephen Ostrow <[EMAIL PROTECTED]> wrote: > >> As long as everyone is voicing their opinions I figured I would be >> another vote for keeping applications. I happen to love being able to >> easily create a front and backend application, and some cases I have more. >> >> When it comes to choosing controllers based on hostname check out this >> wiki page I made which I have heard praise so >> far.http://trac.symfony-project.com/trac/wiki/HowtoChooseApplicationAndEn... >> >> Yes, I know for a production machine being able to get to dev should be >> disabled. >> >> --------------- >> Stephen Ostrow <[EMAIL PROTECTED]> >> >> Matthias N. wrote: >> >>> On 27 Jun., 22:20, "Ian P. Christian" <[EMAIL PROTECTED]> wrote: >>> >>>> Martin Kreidenweis wrote: >>>> >>>>> Hi. >>>>> >>>>>> Can we put the requirement for 'applications' back up for vote? >>>>>> >>>>>> I still see little point in them. >>>>>> >>>>> Now that i've actually just found a sensible way to use them... ;) >>>>> >>>>> It's an intranet application that has "is_secure: on" for the whole app. >>>>> But i needed one module with a different design that can be accessed >>>>> anonymously, still accessing the same database though. Perfect use for a >>>>> separate "application". :) >>>>> >>>> I'd say 'one module' with different design is perfect example of when to >>>> use.. a 'module' ;) >>>> >>>> Perhaps I misunderstand though >>>> >>>> I actually default my entire app. to have is_secure, and often have >>>> modules that require me to set it to not be secure like you seem to have. >>>> >>>> It would clear up a lot of 'how do I use component X from app X in app >>>> Y' and routing issues. >>>> >>>> I'd love to see apps disappear, and have a routing system capable of >>>> working with different hostnames. >>>> >>> I am -1 for dropping applications. This is a very good and useful >>> concept. See applications as different views of your project for >>> different user groups with different requirements. If you don't need >>> multiple apps - what is the problem? Simply use only one. >>> >>> I am +1 for an alternative controller (e.g. index.php) implementation >>> being able to switch to an application based on the host name. We >>> could create a plugin providing a replacement of the default one and >>> some tasks to add/remove/change hostname => application map!? Hm.. I >>> have some existing code that I could use to do that.. :-) >>> >>> Of course it would make sense to integrate this directly with >>> symfony... >>> >>> Regards, >>> Matthias >>> > > > > > > The routing/hostname is not the only limitation concerning application pattern, one more i can think which has been talked both on the forum and on the lists is the sharable modules between applications. Is there a workaround for this yet ?
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
