Even in that rare situation, multiple instances can be created easily, each with the appropriate datasource, all with no modification in the CFC code. Even this tiny use of state vastly improves the portability of the code.
OO doesn't have to be all or nothing. On Feb 7, 2008 10:04 PM, Dominic Watson <[EMAIL PROTECTED]> wrote: >By introducing state to the object > however, you can set the datasource the first time you get an instance of > the component and then never have to worry about it again (unless you are > using multiple datasources which I imagine would be rare in such a > situation). The component is then self contained and as such is more > reusable. -- mxAjax / CFAjax docs and other useful articles: http://www.bifrost.com.au/blog/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;160198600;22374440;w Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:298512 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
