On Saturday, Mar 1, 2003, at 22:38 US/Pacific, samcfug wrote: > But I certainly have a wish list for the server products,
So do we :) http://www.macromedia.com/support/email/wishform/ > and that would be to > incorporate into CF Administrator, provisions for making all the > tweaks and > settings that seem to be giving System Admins so many headaches such > as > settings for stand-alone and multi-homes server settings, etc. Also to > include Well, this discussion's been had here before and there was no real consensus. I think that exposing *all* the possible tweaks would be (a) nearly impossible and (b) make the CF administrator *incredibly* complex! I think it would be bad for the vast majority of CF users who would be overwhelmed by it (and just think of the additional development, QA and documentation cost to Macromedia to do this!). HOWEVER! I agree that certain 'FAQ'-style config options *should* be made part of the CF admin and the cacheRealPath option to which you refer is probably one of those. Part of the issue now is that many of the tweaks are actually J2EE-server specific so it really wouldn't be practical to build them all into the CF admin - the machinery would be different on every J2EE server. > those choices during the install routine. While developers may be > comfortable Good idea (install option for multi-homed). If you haven't already, please submit it to the wishform above. > with modifying this file and that, this is definitely an area that > Network and > System Admins avoid to the extent possible. I'd argue that J2EE admins are extremely used to modifying these sorts of files and that if you are installing CFMX for J2EE on, say, WebSphere or WebLogic, it is not unreasonable to expect the server administrator to be able to do this. Again, I think this is one of those tradeoffs that come around by increasing the power and flexibility of ColdFusion. When this discussion came up last time, I argued that apart from a few key omissions, the CF Admin let you do what 99% of users needed. If you look at the J2EE section of my blog: http://www.corfield.org/blog/archives/cat_j2ee.html you'll see that most of the configuration that I needed to do with CFMX for J2EE was actually in the J2EE server, not CFMX, and so I was dealing with specifics of JRun - you can't expect that sort of functionality to be exposed via CF Admin when it is so app-server dependent. Sean A Corfield -- http://www.corfield.org/blog/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
