Hi Sean,
> On Thursday, Jan 30, 2003, at 07:17 US/Pacific, webguy wrote:
> > Look at Seans excellent rules ..
> > http://www.corfield.org/coldfusion/codingStandards.htm
>
> Thanx. Yes, I highly recommend you use getter/setter methods. Ray gave
> a good reason but wasn't specific. Here's some more detail:
I take it all back :-) Would you recommend using a "value object/(DTO)" [1]
type structure to reduce the number of calls Sean?
>> <cfscript>
>> me = createObject("component","person");
>> me.setFirstName("Sean").setLastName("Corfield");
>> </cfscript>
Interesting, haven't seen that syntax anywhere. Poetic.
WG
[1] for those who want to know. A value object or Data Transfer Object
(design pattern) are often defined as a immutable (sort of/ arguments about
this) object containing the public fields & values of another object. I.E. A
read only structure of Name=Values
It is use in several languages to reduce network traffic.
I.E.
getPerson()
instead of
getFirstname()
getLastname()
etc..
Ok I'm rambling... Read more here:
http://java.sun.com/blueprints/patterns/TransferObject.html
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
This list and all House of Fusion resources hosted by CFHosting.com. The place for
dependable ColdFusion Hosting.
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
