_getTO() returns a Transfer Object, which is essentially a typed struct. I go back and forth between passing around TOs and passing around the actual Beans. It's really just personal preference. The nice thing is that, by using a TO, other parts of the application can't inadvertently call "business methods" on your Bean. The downside is, it's more objects to create (even though Reactor creates them for you). I've heard arguments on both sides of the issue and I'm probably still on the fence.
I suppose the short version of all that is: Pass a Bean (Record) if you want to, or pass a TO if you want to. Don't read too much into it. On 2/5/07, Doug Sims <[EMAIL PROTECTED]> wrote:
In trying to understand service layer CFC's a little better after Brian Kotek's excellent preso at frameworks convention I downloaded his presentation app (http://www.briankotek.com/blog/index.cfm/2007/2/4/Frameworks-Presentation-and-Code-Available ). I noticed he is constantly messing with the _getTO() method on record objects. Could anyone explain what the benefit of returning the TO rather than a record object itself? Thanks! Doug S. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
