Click here to close now.

Welcome!

You will be redirected in 30 seconds or close now.

ColdFusion Authors: Yakov Fain, Maureen O'Gara, Nancy Y. Nee, Tad Anderson, Daniel Kaar

Related Topics: ColdFusion

ColdFusion: Article

Fusebox 4

Fusebox 4

The latest version of Fusebox - version 4 - has been taken out of beta and placed into general availability. Over the last seven years, Fusebox has grown from a collection of best practices and snippets of code into a full-featured, robust framework on which developers can build true Web applications.

Over these seven years, Fusebox has become the overwhelming favorite of ColdFusion developers, and it has been ported to JSP, PHP, and Lasso. Organizations as large as UPS, Casio, Dell Computers, the U.S. Air Force, the U.S. Army, and Rooms to Go employ Fusebox on their Web sites, intranets, and extranets.

Fusebox is built around the idea of a central controller (the Fusebox) that handles requests (fuseactions) and delegates them to smaller, focused controllers (circuits). These components, in turn, delegate work to individual code files (fuses). Fusebox comes with a set of core files (downloadable from fusebox.org) that implement the framework.

Language-Independent XML
This latest version of Fusebox was almost a year in the making, and comes with added features, bug fixes, and improved performance. The most obvious change is in the controller elements. Previously, an fbx_switch.cfm file found in each circuit contained ColdFusion code to determine which actions were to be taken for each request. For example, this code might be used for a login circuit that was meant to respond to the fuseactions, login, and validateLogin (see Listing 1).

In Fusebox 4, the fbx_switch file is replaced with a circuit.xml file. This file has no ColdFusion code; the file consists of nothing but XML (see Listing 2).

Why the move to XML? XML offers Fusebox architects the ability to state their intention without resorting to code. But what's wrong with code? Nothing, of course, but a code-independent XML grammar allows the underlying Fusebox core code to change without affecting the code written for an application. It provides an interface between the architect's intention and the code's implementation.

This means that the core code for, say, a future Fusebox 5 could be substantially different from Fusebox 4, but not break any Fusebox 4 application code. The issue of backwards compatibility must concern providers of any technology. The use of a stable interface that is later translated into implementing code is one of the best ways of dealing with this problem.

XML Grammar
The purpose of the circuit.xml file, where this grammar will be used, is to define the meaning - not the implementation - of a fuseaction. For that reason, the XML grammar set used in these files is quite small; implementation details should be handled by fuses. Even with a constrained grammar set urging them against it, Fusebox architects must be careful to avoid writing implementation code in circuit files. Table 1 lays out the XML elements that can be used in the circuit.xml file.

 

As with all XML, the circuit.xml file must be well-formed - that is, it must conform to the rules for proper XML usage, such as the use of a closing slash in elements that have no closing tag.

While the XML file initially looks very different from Fusebox 3's fbx_switch file, experience among the beta group has shown that adapting to the new format is fast and easy for existing Fuseboxers.

Performance Through Parsing
One of the largest changes to Fusebox is largely invisible to Fusebox programmers. In previous versions of Fusebox, the core files were read on each request and all processing was handled dynamically - that is, at runtime. This created an overhead common to all dynamic processing models.

Fusebox 4 handles things very differently. Much of what had been dynamically determined is now handled in a separate parsing cycle that executes prior to runtime. The Fusebox 4 XML files are parsed and a single file is produced for each fuseaction, using the syntax: parsed.circuitname.fuseactionname.cfm. All such files are automatically placed in a parsed directory.

At runtime, index.cfm (or whatever the default file is) calls the Fusebox 4 runtime file, fusebox40.runtime file. The first job of the runtime file is to ensure that the parsing cycle has been run - and that no changes to XML files have been introduced since the time last parsed. If the runtime file code determines that the parsed files are not up to date (or are missing altogether), it calls fusebox40.loader, fusebox40.parser, and fusebox40.transformer, all of which work together to produce the parsed files located in the parsed directory.

By preparsing the code, the runtime logic needs only to include the appropriate parsed file. That is, if a request is made of the application to execute the fuseaction, home.main, for example, the runtime code (once it has assured itself that the existing state of parsed files is current) includes the file, parsed/parsed.home.main.cfm. By resolving as many dynamic issues as possible before runtime, performance is greatly improved.

Extending Fusebox with Plug-ins
Fusebox 4 also introduces the idea of plug-ins. Plug-ins provide developers a way of extending Fusebox's core functionality without having to tinker with the core Fusebox code. If the Fusebox core file is written to accommodate virtually any developer working on any project, and the application code is written to deal with individual fuseaction requests, plug-ins inhabit the middle ground - code that should run across multiple fuseactions within an application.

What can plug-ins do? Virtually anything - from logging requests to implementing security to... well, anything. Plug-ins allow the programmer to add application-wide functionality that the Fusebox core designers did not or could not anticipate.

Once the plug-in code is written, it is placed in the plug-ins directory. The plug-in designer determines at which of six plug-in points he or she wishes the plug-in code to run. This decision is registered in another XML file, fusebox.xml, located in the root directory.

The plug-in points reflect different stages of a fuseaction life cycle, such as preprocess (before anything else happens), prefuseaction (immediately prior to a fuseaction call), postfuseaction, and postprocess. The other two plug-in points are not temporally based, but occur when exceptions occur.

Plug-ins provide great extensibility to Fusebox without compromising the integrity of the Fusebox core files. During the beta cycle, several members wrote plug-ins to deal with common issues (such as security) and we expect to see plug-ins used as commonly as custom tags.

Exceptions, Layouts, Accessibility, and Content Components
As good as Fusebox 3 was, it suffered from one unfortunate liability: its exception handling was poor, and Fuseboxers have suffered with obscure exception messages since its release. Built into Fusebox 4 is the ability for the programmer to specify a module to call when an exception is thrown. The particulars of handling exceptions can then be handled by a plug-in. This provides enormous flexibility for a wide variety of needs.

Layouts in Fusebox 3 were exceptionally helpful. In Fusebox 4, they just get better. While Fusebox 3 tied layouts to the physical directory structure, this restriction is gone in Fusebox 4. Layout files lose their special status and simply become a fuseaction, making them easier to build and to employ.

While Fusebox 3 existed uneasily with ColdFusion's tag, this is no longer the case; developers needing to use can do so with impunity. The changes made to layouts also make Fusebox 4 more accessible to users with visual impairments by supporting Section 508 accessibility standards. Especially for government agencies - often charged with "508" issues - this represents a breakthrough.

Fusebox 4 also introduces the idea of granularizing content by providing content component variables that can be combined to form a larger Web page. Content component variables (CCVs) allow fuseactions to concentrate on building pieces of content while deferring the placement and usage of these components to another fuseaction. One obvious use for this technology is the building of portal-style pages, but it can be used whenever developers want to make display code more reusable. CCVs allow for far greater reusability of these components than was available previously.

Is Fusebox 4 for You?
So, with all this "new stuff," how disruptive is the move from Fusebox 3 to Fusebox 4? Surprisingly, not very. In a typical Fusebox application, well over 90% of code written is in fuses. None of this code changes at all. Members of the Fusebox 4 beta group were pleased by how simple porting Fusebox 3 applications to Fusebox 4 was. One member related that an application that had taken over a month to build was upgraded to Fusebox 4 in less than two hours.

Is Fusebox 4 for everyone? Certainly not. Some developers have created their own frameworks that work well for them and their team. Some chafe at the idea of working within any framework. Still others want to use a true object-oriented framework, while Fusebox 4 is solidly procedural. (For more information on an object-oriented framework see the article in the August issue of CFDJ, "Mach-II: Breaking the Procedural Barrier, Vol. 5, issue 8.")

Is Fusebox for you? Of course, you're the only one who can make that judgment, but if you're looking for a powerful, robust, mature framework on which to build solid ColdFusion applications, Fusebox 4 definitely deserves your attention. For more information, including sample applications and core code, visit fusebox.org. If you're interested in attending the Fusebox conference in Las Vegas, visit www.cfconf.org/fusebox2003.

Note: Thanks to John Quarto, Brian Kotek, Sandy Clark, Perry Woodin, and Brian LeRoux for making available to me a pre-release copy of their upcoming book, Discovering Fusebox 4, available at techspedition.com.

More Stories By Hal Helms

Hal Helms is a well-known speaker/writer/strategist on software development issues. He holds training sessions on Java, ColdFusion, and software development processes. He authors a popular monthly newsletter series. For more information, contact him at hal (at) halhelms.com or see his website, www.halhelms.com.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@ThingsExpo Stories
We certainly live in interesting technological times. And no more interesting than the current competing IoT standards for connectivity. Various standards bodies, approaches, and ecosystems are vying for mindshare and positioning for a competitive edge. It is clear that when the dust settles, we will have new protocols, evolved protocols, that will change the way we interact with devices and infrastructure. We will also have evolved web protocols, like HTTP/2, that will be changing the very core of our infrastructures. At the same time, we have old approaches made new again like micro-services...
Operational Hadoop and the Lambda Architecture for Streaming Data Apache Hadoop is emerging as a distributed platform for handling large and fast incoming streams of data. Predictive maintenance, supply chain optimization, and Internet-of-Things analysis are examples where Hadoop provides the scalable storage, processing, and analytics platform to gain meaningful insights from granular data that is typically only valuable from a large-scale, aggregate view. One architecture useful for capturing and analyzing streaming data is the Lambda Architecture, representing a model of how to analyze rea...
Today’s enterprise is being driven by disruptive competitive and human capital requirements to provide enterprise application access through not only desktops, but also mobile devices. To retrofit existing programs across all these devices using traditional programming methods is very costly and time consuming – often prohibitively so. In his session at @ThingsExpo, Jesse Shiah, CEO, President, and Co-Founder of AgilePoint Inc., discussed how you can create applications that run on all mobile devices as well as laptops and desktops using a visual drag-and-drop application – and eForms-buildi...
Docker is an excellent platform for organizations interested in running microservices. It offers portability and consistency between development and production environments, quick provisioning times, and a simple way to isolate services. In his session at DevOps Summit at 16th Cloud Expo, Shannon Williams, co-founder of Rancher Labs, will walk through these and other benefits of using Docker to run microservices, and provide an overview of RancherOS, a minimalist distribution of Linux designed expressly to run Docker. He will also discuss Rancher, an orchestration and service discovery platf...
SYS-CON Events announced today that Vitria Technology, Inc. will exhibit at SYS-CON’s @ThingsExpo, which will take place on June 9-11, 2015, at the Javits Center in New York City, NY. Vitria will showcase the company’s new IoT Analytics Platform through live demonstrations at booth #330. Vitria’s IoT Analytics Platform, fully integrated and powered by an operational intelligence engine, enables customers to rapidly build and operationalize advanced analytics to deliver timely business outcomes for use cases across the industrial, enterprise, and consumer segments.
SYS-CON Events announced today that Dyn, the worldwide leader in Internet Performance, will exhibit at SYS-CON's 16th International Cloud Expo®, which will take place on June 9-11, 2015, at the Javits Center in New York City, NY. Dyn is a cloud-based Internet Performance company. Dyn helps companies monitor, control, and optimize online infrastructure for an exceptional end-user experience. Through a world-class network and unrivaled, objective intelligence into Internet conditions, Dyn ensures traffic gets delivered faster, safer, and more reliably than ever.
Containers and microservices have become topics of intense interest throughout the cloud developer and enterprise IT communities. Accordingly, attendees at the upcoming 16th Cloud Expo at the Javits Center in New York June 9-11 will find fresh new content in a new track called PaaS | Containers & Microservices Containers are not being considered for the first time by the cloud community, but a current era of re-consideration has pushed them to the top of the cloud agenda. With the launch of Docker's initial release in March of 2013, interest was revved up several notches. Then late last...
CommVault has announced that top industry technology visionaries have joined its leadership team. The addition of leaders from companies such as Oracle, SAP, Microsoft, Cisco, PwC and EMC signals the continuation of CommVault Next, the company's business transformation for sales, go-to-market strategies, pricing and packaging and technology innovation. The company also announced that it had realigned its structure to create business units to more directly match how customers evaluate, deploy, operate, and purchase technology.
In their session at @ThingsExpo, Shyam Varan Nath, Principal Architect at GE, and Ibrahim Gokcen, who leads GE's advanced IoT analytics, focused on the Internet of Things / Industrial Internet and how to make it operational for business end-users. Learn about the challenges posed by machine and sensor data and how to marry it with enterprise data. They also discussed the tips and tricks to provide the Industrial Internet as an end-user consumable service using Big Data Analytics and Industrial Cloud.
Performance is the intersection of power, agility, control, and choice. If you value performance, and more specifically consistent performance, you need to look beyond simple virtualized compute. Many factors need to be considered to create a truly performant environment. In his General Session at 15th Cloud Expo, Harold Hannon, Sr. Software Architect at SoftLayer, discussed how to take advantage of a multitude of compute options and platform features to make cloud the cornerstone of your online presence.
The explosion of connected devices / sensors is creating an ever-expanding set of new and valuable data. In parallel the emerging capability of Big Data technologies to store, access, analyze, and react to this data is producing changes in business models under the umbrella of the Internet of Things (IoT). In particular within the Insurance industry, IoT appears positioned to enable deep changes by altering relationships between insurers, distributors, and the insured. In his session at @ThingsExpo, Michael Sick, a Senior Manager and Big Data Architect within Ernst and Young's Financial Servi...
Even as cloud and managed services grow increasingly central to business strategy and performance, challenges remain. The biggest sticking point for companies seeking to capitalize on the cloud is data security. Keeping data safe is an issue in any computing environment, and it has been a focus since the earliest days of the cloud revolution. Understandably so: a lot can go wrong when you allow valuable information to live outside the firewall. Recent revelations about government snooping, along with a steady stream of well-publicized data breaches, only add to the uncertainty
The explosion of connected devices / sensors is creating an ever-expanding set of new and valuable data. In parallel the emerging capability of Big Data technologies to store, access, analyze, and react to this data is producing changes in business models under the umbrella of the Internet of Things (IoT). In particular within the Insurance industry, IoT appears positioned to enable deep changes by altering relationships between insurers, distributors, and the insured. In his session at @ThingsExpo, Michael Sick, a Senior Manager and Big Data Architect within Ernst and Young's Financial Servi...
PubNub on Monday has announced that it is partnering with IBM to bring its sophisticated real-time data streaming and messaging capabilities to Bluemix, IBM’s cloud development platform. “Today’s app and connected devices require an always-on connection, but building a secure, scalable solution from the ground up is time consuming, resource intensive, and error-prone,” said Todd Greene, CEO of PubNub. “PubNub enables web, mobile and IoT developers building apps on IBM Bluemix to quickly add scalable realtime functionality with minimal effort and cost.”
The Internet of Things (IoT) is rapidly in the process of breaking from its heretofore relatively obscure enterprise applications (such as plant floor control and supply chain management) and going mainstream into the consumer space. More and more creative folks are interconnecting everyday products such as household items, mobile devices, appliances and cars, and unleashing new and imaginative scenarios. We are seeing a lot of excitement around applications in home automation, personal fitness, and in-car entertainment and this excitement will bleed into other areas. On the commercial side, m...
Sensor-enabled things are becoming more commonplace, precursors to a larger and more complex framework that most consider the ultimate promise of the IoT: things connecting, interacting, sharing, storing, and over time perhaps learning and predicting based on habits, behaviors, location, preferences, purchases and more. In his session at @ThingsExpo, Tom Wesselman, Director of Communications Ecosystem Architecture at Plantronics, will examine the still nascent IoT as it is coalescing, including what it is today, what it might ultimately be, the role of wearable tech, and technology gaps stil...
Every innovation or invention was originally a daydream. You like to imagine a “what-if” scenario. And with all the attention being paid to the so-called Internet of Things (IoT) you don’t have to stretch the imagination too much to see how this may impact commercial and homeowners insurance. We’re beyond the point of accepting this as a leap of faith. The groundwork is laid. Now it’s just a matter of time. We can thank the inventors of smart thermostats for developing a practical business application that everyone can relate to. Gone are the salad days of smart home apps, the early chalkb...
In the consumer IoT, everything is new, and the IT world of bits and bytes holds sway. But industrial and commercial realms encompass operational technology (OT) that has been around for 25 or 50 years. This grittier, pre-IP, more hands-on world has much to gain from Industrial IoT (IIoT) applications and principles. But adding sensors and wireless connectivity won’t work in environments that demand unwavering reliability and performance. In his session at @ThingsExpo, Ron Sege, CEO of Echelon, will discuss how as enterprise IT embraces other IoT-related technology trends, enterprises with i...
When it comes to the Internet of Things, hooking up will get you only so far. If you want customers to commit, you need to go beyond simply connecting products. You need to use the devices themselves to transform how you engage with every customer and how you manage the entire product lifecycle. In his session at @ThingsExpo, Sean Lorenz, Technical Product Manager for Xively at LogMeIn, will show how “product relationship management” can help you leverage your connected devices and the data they generate about customer usage and product performance to deliver extremely compelling and reliabl...
The Internet of Things (IoT) is causing data centers to become radically decentralized and atomized within a new paradigm known as “fog computing.” To support IoT applications, such as connected cars and smart grids, data centers' core functions will be decentralized out to the network's edges and endpoints (aka “fogs”). As this trend takes hold, Big Data analytics platforms will focus on high-volume log analysis (aka “logs”) and rely heavily on cognitive-computing algorithms (aka “cogs”) to make sense of it all.