> This is exactly what I'm doing. I'm rebuilding the app that I use for my > blog. It was running with one monolithic cfc (over a thousand lines of > code), that contained public and administrative functionality. > > My plan is twofold, separate the monolith into individual components based > on functionality, and secondly secure the administrative functions by moving > them into a password protected part of the site, so they're not accessible > from the outside, and also, by making them private, ensuring that they'll > only be accessible from inside the app.
Given that description, I don't see a clear value to taking the private methods and moving them outside of the components that will call them, if those methods don't logically belong to a separate object. It definitely makes sense for those methods to be private, but going back to your original question I don't see the benefit in creating a separate class just with those methods in it for each public class that would end up extending that class. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsit ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:346563 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
