If you wait just a short time then the new steering and standards committees
will be in place and you can suggest your change, and possibly have it
adopted for the new core files. There are some people out there who have
already customized their core files for some things, and while generally not
recommended, it's not exactly illegal.

Tim Heald
ACP/CCFD :)
Application Development
www.schoollink.net

> -----Original Message-----
> From: Justin Scott [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 11, 2002 11:50 AM
> To: [EMAIL PROTECTED]
> Subject: Invalid Fuseaction Handling
>
>
> I'm just getting into Fusebox 3.x development and have come
> across something
> I would like some input on.  In FB 3, the "circuit.fuse" method
> of handling
> the fuseaction attribute is great, but if the value passed is missing a
> period, an error is generated instead of execution being passed to the
> cfdefaultcase in the switch.  This bothers me, as it creates a very easy
> opportunity for someone to generate a CF error on purpose.
>
> I have determined that a simple change to the core fusebox code
> (in section
> 8) to handle this specifically would work, but everything I've
> read says to
> NOT change the core code or weird/bad/evil things may happen.
>
> I'm wondering if anyone else sees this as a big issue and how you
> handle it,
> core code mods or not.  Thanks!
>
> -Justin Scott, Lead Developer
>  Sceiron Internet Services, Inc.
>  http://www.sceiron.com
>
>
>
> PS: I'm new on the list, so I'm sorry if this has been covered already.
>
>


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


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

Reply via email to