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]

615-834-1876

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.bVUysT
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
==^================================================================


==^================================================================
This email was sent to: archive@jab.org

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
==^================================================================

Reply via email to