Yes, go for C; use object composition, so that the contactinfo instance is a property of the user instance.
On 1/4/06, Bobby Hartsfield <[EMAIL PROTECTED]> wrote: > I'd agree with that. I'd personally lean more towards example C though. > Since users can't exist without contact info, I don't see anything wrong > with modifying USER.cfc to encompass CONTACTINFO.cfc so long as it doesn't > hose the CONTACTINFO.cfc as a stand alone component. There's definitely > nothing wrong with simplifying matters :-) -- CFAJAX docs and other useful articles: http://jr-holmes.coldfusionjournal.com/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:228320 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
