Technically this is not a duplicate of Code, because you are separating the
database away from the service/business logic. This means that if you go
from transfer/reactor over to CF-ORM you are essentially just removing that
tier and replacing it.

And it also promotes code reuse of the database tier. Because you may have
logic in your service layer to do something different with the results, in
more than one case of logic. But the code to return the result doesn't
change.

So there is potentially two things you are doing, re-use of code and easy
abstraction and removal if the need ever arises for something better.

-- 
Regards,
Andrew Scott
WebSite: http://www.andyscott.id.au/
Google+: http://plus.google.com/108193156965451149543





On Wed, Jan 11, 2012 at 3:15 PM, Gavin Baumanis <beauecli...@gmail.com>wrote:

> Sure thing.
>
> gavinsManagerCFC
> ...
> <cffunction name="getgavinsObject">
>     <cfargument name = "ag1" required="true"... >
>     <cfargument name = "ag2 required="true"... >
>
>     <cfreturn gavinsDAOCFC.getGavinsObject(arg1 = "#arguments.arg1#, arg2
> = "#arguments.arg2# >
> </cffunction>
>
>
> gavinsDAOCFC
> ...
>  <cffunction name="getgavinsObject">
>     <cfargument name = "ag1" required="true"... >
>     <cfargument name = "ag2 required="true"... >
>
>     ... Some SQL
>         WHERE column1 = "#arguments.arg1#"
>        AND column2 = "#arguments.arg2#"
>
>     return something (maybe)
> </cffunction>
>
> In this case the getGavinsObject in gavinsManagerCFC is "practically" a
> stub / duplication of the function in the DAO.
> The argument is why bother?
>
> Why not just call the DAO version of the CFC and do away with the
> managerCFC entirely?
>
>
> Gavin.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"cfaussie" group.
To post to this group, send email to cfaussie@googlegroups.com.
To unsubscribe from this group, send email to 
cfaussie+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/cfaussie?hl=en.

Reply via email to