As Sean noted, Services often contain logic that operates on a layer above that of domain objects. These can include transactions or business rules, etc. So they act as more than just a Facade. Service Layer is a pattern in its own right, and Fowler's "Patterns of Enterprise Application Architecture" has a section devoted to it.
On 10/20/07, Paul Marcotte <[EMAIL PROTECTED]> wrote: > > Great conversation fellas. > > @Brian I don't wan to muddy the waters with mixed terminaology, bu is it > save to say that a Service is essentially a Facade? Since it is basically > "a unified interface to a set of interfaces in a subsystem..." > > Paul > > On 10/20/07, Brian Kotek <[EMAIL PROTECTED]> wrote: > > > > On 10/20/07, Alan Livie <[EMAIL PROTECTED] > wrote: > > > > > > > > > I'm fairly new to OO myself so don't treat this as best practice!! :-) > > > > > > > > No, do treat it as best practice. ;-) > > > > > > > > > -- > Paul Marcotte > Fancy Bread - in the heart or in the head? > http://www.fancybread.com > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
