On Feb 3, 2008 1:00 PM, Mark Mandel <[EMAIL PROTECTED]> wrote: > That is a really interesting post!
I should blog it I suppose... > > Fifth, I'm starting to use a BaseGateway CFC that uses > > onMissingMethod() to implement a number of common persistence methods ... > Just to clarify, your Gateway objects essentially act as your service layer > from the get go. As you develop, you could end up implementing a > getVendorById(), in case you wanted to provide custom logic if it is > required. Would that be correct? Well, it definitely blurs the boundaries a little. Right now I'm still keeping a separate service layer and gateway layer so my service layer also "implements" some of these methods so that the controller layer can ask the service layer for those objects. I'm still in two minds about how best to handle that duplication. Part of me leans toward simply adding onMissingMethod() to my service CFC and having it attempt to call missing methods directly on the gateway for certain method patterns like get*ById() and find*(). However, most of my services actually do have a completely different set of methods so it's not quite that straightforward. My services support my high-level application needs whereas my gateways support my low-level application needs. For example, one of my client projects has 11 controllers, 27 service CFCs, 14 data gateway CFCs so you can see that there are no 1:1 relationships here. -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" 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/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
