That is kind of what I was thinking as well. It just seems (for this project at least) that a Service layer may be too much extra work. However, the application does have some planned future releases with more functionality. So does the Service layer sit inside the application folder?
So say I have the root com folder and a root project folder called "fooProject". Does the service layer live inside the fooProject folder? >from my experience, you'd usually have a service layer CFC. This service >layer would be responsible for everything in its domain, eg, >CustomerService.cfc would be responsible for creating a Customer instance >where Customer could be composite. CustomerService.cfc would also expose >gateways and such thus its really a Customer API in a way. This >CustomerService.cfc would inject the DSN when creating the DAO's and >Gateways needed. Note that if Customer is composed of data and say a >instance of Address, CustomerService.cfc would work with address cfcs too >and you probably wouldn't need a AddressService.cfc. I usually further put >a remote facade for Flex to talk to that is in short the full API exposed to >the Flex client only. > >my $0.02 > >DK > >On 4/25/07, Kyle Hayes <[EMAIL PROTECTED]> wrote: >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 by Adobe® Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7. Free Trial. http://www.adobe.com/products/coldfusion?sdid=RVJV Archive: http://www.houseoffusion.com/groups/Flex/message.cfm/messageid:3945 Subscription: http://www.houseoffusion.com/groups/Flex/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.37
