'glue' patterns for wiring together various php frameworks
Posted: Fri Dec 04, 2009 12:56 am
hey php peops --
noob question (just migrated to open sauce from many years as M$ dev. Finally jumped in the pool.):
Im trying to come up with a decent and simple pattern for 'gluing' together various php frameworks. Mostly I'd like to be able to swap them out if needed later on.
For now Im looking at using say, OWASP php, phpGroupware, outlet ORM, phpMvc, and phpGacl or flow3. Of course I need write my code to wire/glue all these FWs together to play nice with one another...
....obviously Facade pattern comes to mind. Write an interface/facade module for each framework to site between my code and the FWs to insulate from future changes in the frameworks. But, that seems like lots of work to consolidate each framework, considering I really don't even know the FWs that well myself just yet. (and I may get 2 weeks into writing a facade and swap/test/discover/change to an alternate framework or two while Im in the 'php noob' stage)
IOC/DI will probably come in handy at some point, thus flow3 framework, mimicking Spring. (If it breaks out of alpha, beta, ga-ga land, that is.)
What patterns/designs/best practices are you all currently using to ease the pain of:
1. having so many great choices of available FWs? (unheard of in M$ world. It's usually RYO/DIY all the way there)
2. organizing the directories off root with them (lots of name scheme clashes in Asp classic includes)
3. gluing them together with some kind of harmony and simplicty.
just curious.
noob question (just migrated to open sauce from many years as M$ dev. Finally jumped in the pool.):
Im trying to come up with a decent and simple pattern for 'gluing' together various php frameworks. Mostly I'd like to be able to swap them out if needed later on.
For now Im looking at using say, OWASP php, phpGroupware, outlet ORM, phpMvc, and phpGacl or flow3. Of course I need write my code to wire/glue all these FWs together to play nice with one another...
....obviously Facade pattern comes to mind. Write an interface/facade module for each framework to site between my code and the FWs to insulate from future changes in the frameworks. But, that seems like lots of work to consolidate each framework, considering I really don't even know the FWs that well myself just yet. (and I may get 2 weeks into writing a facade and swap/test/discover/change to an alternate framework or two while Im in the 'php noob' stage)
IOC/DI will probably come in handy at some point, thus flow3 framework, mimicking Spring. (If it breaks out of alpha, beta, ga-ga land, that is.)
What patterns/designs/best practices are you all currently using to ease the pain of:
1. having so many great choices of available FWs? (unheard of in M$ world. It's usually RYO/DIY all the way there)
2. organizing the directories off root with them (lots of name scheme clashes in Asp classic includes)
3. gluing them together with some kind of harmony and simplicty.
just curious.