I do just that with my CMS product a single repositry for my CFCs and admin templates which means that updates are made once and are global.
The only issue I have has with this is when it comes to special requiremenst with clients and theere are customizations for particular applications. So far I have had no issues with it, especially as I am still building on the functionality of the app, i can build in one spot and broadcast the changes globaly from one spot aswell. Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jamie Lawrence Jenner Sent: Tuesday, May 25, 2004 12:53 AM To: CFAussie Mailing List Subject: [cfaussie] a viable option? Hi all, I have recently devloped an e commerce app, which is to be used by numerous retailers. The app is going to be updated regularly, as will all sites using it. As all apps are using the same components, includes and modules, I have thought that instead of having say, four sites each with their own components, is having the components all within a central area and creating a mapping in cf to point to them. then createing component objects based on this mapping. This would then make it easier to update any components, as it is only to be done centrally. I realise that there could be a load bearing issue if there were a high amount of sites using the CFC's, but none of the sites will have high usage for a while So, is this a viable option? If yes why? If no why? i would be greatful for any opinions/other methods on this matter Cheers Jamo --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004 --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
