Unfortunately though, Rob's really long index doesn't appear to use Fusebox 3's "core file", which I assume, is the "complex machinery" you mention, Sean. In pre-FB3, there is very little to no machinery used, so long cfswitch statements are the result of the poor design of whoever wrote unfortunate Rob's code, not some implied Fusebox architectural path. But that's not to say there aren't certain aspects of FB3's "machinery" that I'm looking forward to optimizing towards OO/CFCs/Java :)
I have encountered this same limitation in CFMX/Java in a really long custom tag written by (surprise) someone else. Sean, do you know if this (64k) limitation is something that can be addressed by Macromedia? Or is it inherent to Java? Or... ? NAT > -----Original Message----- > From: Sean A Corfield [mailto:[EMAIL PROTECTED]] > Sent: Monday, September 30, 2002 4:07 PM > To: CF-Talk > Subject: Re: Switching to CFMX > > > I've been trying to resist responding to this thread but... > > On Monday, Sep 30, 2002, at 14:44 US/Pacific, Rob Rohan wrote: > > <cfswitch switch="attributes.fuseaction"> > > <cfcase value="listall,showone,dosomething,doanotherthing" > > delimiters=","> > > <cfinclude template="index0.cfm"> > > </cfcase> > > <cfcase value="update,delete,dothis,dothat" delimiters=","> > > <cfinclude template="index1.cfm"> > > </cfcase> > > ... > > </cfswitch> > > Let me say, first of all, that I'm glad you've found a workaround. > > Secondly, this is exactly the sort of issue that makes me very nervous > of Fusebox. It tries hard to hide complexity from programmers but this > shows just how much code it's really hiding and just how much machinery > lurks behind the framework. Of course, this isn't really FB's fault: > old-style CF just doesn't provide the expressive machinery to support > the sort of near-OO encapsulation that FB attempts. I think that FB4 > has the potential to be much cleaner and idiomatic, based on the OO > features that MX introduced to CF. I'm looking forward to seeing it. > > > It adds a whole layer of abstraction, but seems to work. Again this > > only > > happen when doing really large files and the (evil) errors MX gives > > are the > > following > > This is good to know for other Fuseboxers. Thanx for following up with > a workaround without 'bashing' CF! > ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
