If Dept B's features are similar to A's, why not add their functionality to the same CFC? It seems that much code would be the same between the two departments, so I would not duplicate it, if at all possible. I would probably create a common CFC then, if needed, create specialized CFCs for each department that consume the common CFC. M!ke
_____ From: Matthew Small [mailto:[EMAIL PROTECTED] Sent: Mon 12/27/2004 7:11 AM To: CF-Talk Subject: Single application - multiple users with differing specifications Hi there, I already have my own ideas, but I would appreciate this list's as well. Let's say I have an application that I've written for department A. Now department B wants the same application but needs to add or delete features. I don't want to change the functionality for department A, and copy/paste for the application isn't a good idea either. I know that CFCs are kind of a way to accomplish this, but when adding a new feature that needs to have a presentation element modified, it seems like copy/paste is as good of a solution for this as extending a CFC. What are your views on this? Thank you, Matthew Small Web Developer American City Business Journals 704-973-1045 [EMAIL PROTECTED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Gold Sponsor - CFHosting.net http://www.cfhosting.net Message: http://www.houseoffusion.com/lists.cfm/link=i:4:188803 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
