Perhaps a solid A.O.P. solution in the framework looks like what's needed here.
http://en.wikipedia.org/wiki/Aspect-oriented_programming So plugin developers get their functionality running without stepping on eachothers feet. So Does that mean Symfony needs or is lacking an AOP component? [Some other frameworks like SEAM have them] On Jun 18, 4:06 pm, Bernhard Schussek <[email protected]> wrote: > A perfect example of why one should program against interfaces, not classes. > > I don't see how the observer pattern could help you. > > I see a solution though. You can make a composition of all the > plugin's user classes in your myUser class (i.e. store them in > properties). Then implement the __call() method and forward any > unknown method call to the nested user object that has this method. > > This will only work though if none of the plugins actually require the > myUser class to technically extend the plugin user classes (f.i. by > use of instanceof or through type hints). > > Bernhard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
