I see your point Kay and you are right on that for sure. But one of my fusedocs because of the complex nature of the action file is about 75+ lines long. Frankly I think it has way too many form fields to process but it does have to be done for this application. Hence the root of the question.
Lee Foster (e)consultant, Web developer, Web Architect [EMAIL PROTECTED] 615-834-1876 http://www.l3enterprises.com Nashville, TN -----Original Message----- From: Kay Smoljak [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 01, 2002 7:55 PM To: [EMAIL PROTECTED] Subject: RE: Fusedoc-ing Exceptions I think the biggest issue with file size is the time it takes the server to serve the file to the browser, not the time it takes the server to load the file off the local file system. I use <cfsilent> around all my FuseDocs (and qry and act fuses too) so my output HTML is quite tight. I don't think leaving the FuseDocs in there makes much of a difference. K. -----Original Message----- From: David Huyck [mailto:[EMAIL PROTECTED]] Sent: Thursday, 2 May 2002 6:14 AM To: [EMAIL PROTECTED] Subject: Re: Fusedoc-ing Exceptions Well, maybe, but I'd say a better approach, if you really think your comments are slowing down the server, would be to strip all comments out of files when you upload them to the server. You could write a script that strips all the comments out of your files and re-saves them in a different directory for uploading. Personally, when I am developing, if I have to go to a separate file to get the comments on this file, that seems like a poor way to organize my code and my time. Before you go and do anything, though, it would be a good idea to do some benchmarks, I think. Figure out if a file with HUGE comments is really a big deal, or if that is just a supposition. David Huyck [EMAIL PROTECTED] ----- Original Message ----- From: "Lee Foster" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 01, 2002 3:34 PM Subject: RE: Fusedoc-ing Exceptions I have an opinion style question. I know and understand the purpose of fusedocs and by no way I'm I against it. (Trying to dodge any possible bullets). Ok here is the question. On a web server with a heavy load is it possible that the increase file size could cause or aid in performance issues. In this case would it be better to create a separate file with the fusedoc and make a single line reference in the template to it. God I hope this doesn't start another silly battle, Lee Foster (e)consultant, Web developer, Web Architect [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 615-834-1876 http://www.l3enterprises.com <http://www.l3enterprises.com/> Nashville, TN -----Original Message----- From: Steve Nelson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 01, 2002 2:41 PM To: [EMAIL PROTECTED] Subject: Re: Fusedoc-ing Exceptions Jared- That's an interesting idea. I wonder if it should be part of the in/out IO section? Like <cfthrow>s for the <out>s and <cfcatch>s for the <in>s. I don't know, this is something we should play around with more. Steve Nelson Jared Stark wrote: This is probably something that has been discussed on the fbsteer list, but since I can barely make it through all my emails as it is I don't subscribe to it. I'm wondering about fusedoc-ing exceptions that may be thrown within a template, specifically I mean user defined exceptions.For example, in my fuses if an attribute is missing I will throw a 'com.mycompany.attributes.MissingAttributesException'.I would like to document that somehow so that A) the developer writing the fuse knows about it, and B) a developer using the fuse will know about the exception and can gracefully handle it (hopefully).I imagine something like: <exceptions> <exception type=" com.mycompany.Attributes.MissingAttributeException" onCondition="A required attribute is missing" comments="" /> etc. </exceptions> Has something like this been proposed? How does everyone currently document exceptions?*Does* anyone currently document exceptions, or am I (yet again) up in the night? Thanks, Jared ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
