Fuse Box
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Fuse Box as PDF for free.
More details
- Words: 1,172
- Pages: 20
Prelude to Fusebox Prerequisite Understanding: / Variable scopes: session/client/application/request/attributes/ca ller Custom tags URLToken If you don’t understand any of these, please tell me!
An Introduction to Fusebox Methodology and Techniques Finally – A True Standard for ColdFusion’s Most Proven and Popular Application Architecture Presented by Nat Papovich – Webthugs Consulting Developed by the Fusebox Community including Hal Helms, Jordan Clark, Steve Nelson, Fred Sanders, Jeff Peters, Russ
Why Fusebox? What Is Fusebox? Structured architecture - scalability, maintainability, modularity Facilitates team development Self-documents your application Allows repeatability Large community Proven but evolving Community-driven Extensible - Fusebox for PHP, JSP, ASP Quick to learn Free
General Fusebox Theory Index.cfm is controller - all interaction goes through the Fusebox via Fuseactions Multiple index.cfms for sections of the site, called circuits Root index.cfm handles global variables, root requests Index.cfm acts via cfcase, including files (fuses) and logic If a circuit blows up, the entire site is not blacked out Electrical fuse box metaphor Circuits are modular, thus reusable New Extended Fusebox (Hal-style) standard calls for no home application: All circuits standalone with individual cfapplication tags and no global variable dependencies – cfparam all vars All circuit index.cfms are cfincluded, not
First Steps (Pre-Coding) 1. Produce a quality specification
Nothing Fusebox specific here Be on the lookout for Secretagents.com spec tool
2. Use fUseML or another modeling tool to make the design including directory structure
fUseML is derived from the UML Build design taking index.cfm interaction (Fuseactions) into account
3. Create stringent Fusedocs for all fuses
Fuses should not be dependant on any variables not explicitly stated Make assertions if necessary
Creating A Fusebox Application
Create the index.cfm files Create Fuseactions in index.cfm Create Fusedocs for fuses Write fuses Stand back and marvel
Create the Index.cfm Files Every directory (circuit application) has one index.cfm file Index.cfm controls all the Fuseactions of that circuit application It is the Fusebox All links and form submissions go to the index.cfm It is a single cfswitch statement with multiple cfcase statements Each cfcase is a different Fuseaction
The Fusebox Code ....
More on the custom tag later…
Model-View-Controller Approach Request
This is Meant to Be Just text That isn’t Clear. I hope It works the Way I want It to.
cf_do_logic
(model)
Fusebox (controller) This is Meant to Be Just text That isn’t Clear. I hope It works the Way I want It to.
dsp_UserLogin.cfm
Name: Stan Cox Intelligence: Monumental Bravery: Stunning
HTML Returned
(view)
Create the Fuseactions A Fuseaction may cfinclude .htm/.cfm; cfmodule; cflocation; contain limited cfml A Fuseaction may NOT display anything to the browser or contain “open” SQL
Determine what steps are needed to complete each Fuseaction Add those steps inside each cfcase statement
File Naming Conventions (Fuses) app_globals.cfm – File defines variables, instantiates application request.mainDSN, request.webroot, request.mypath
dsp_filename.cfm - Display file
Only file that contains HTML or any output to browser
act_filename.cfm - Action file
Only file allowed to perform actions on the database – updates, inserts, deletes, selects allowed, but only in conjunction with action
qry_filename.cfm - Query file
Extremely modular file can be called “willy-nilly” throughout application, performs selects on database
Fusedoc Documentation Standard A Fusedoc outlines responsibilities, customizations, and expectations of fuses, and is unique to each fuse No fuse can assume the existence of any variable unless it is noted in the Fusedoc for that fuse Once completed, a Fusedoc should provide all the information needed to code the fuse – no interaction with application architects or previous specifications should be needed A Fusecard contains the following elements: Name of the file Responsibilities (non-technical, plain English, derived from the application design/fUseML) Author / coder Variables list (incoming, outgoing, and persistent)
Fusedoc Legend --> <-<-> ++>
explicitly passed incoming parameter explicitly passed outgoing parameter pass-thru parameter (unchanged) existing persistent parameter (session, client, etc.) <++ created persistent parameter +++ included file [parameter] brackets indicates optional Examples: --> CurrentUser: a WDDX STRUCTURE <-- [badLogin]: optional, a STRING <++ Session.ColorChoice: a STRING (Red|Blue) <-> UserID: an INTEGER +++ myGlobals.cfm
Create the Necessary Fuses Because the Fusedocs are so carefully built, and the design so thoroughly thought out, individual fuses can be “farmed out” for coding Remember – all links and form actions go to index.cfm, specifying which Fuseaction to perform; never to the specific dsp or act files. Javascript:window.location=‘index.cfm?fuseaction=Buy’
An Introduction to Fusebox Methodology and Techniques Finally – A True Standard for ColdFusion’s Most Proven and Popular Application Architecture Presented by Nat Papovich – Webthugs Consulting Developed by the Fusebox Community including Hal Helms, Jordan Clark, Steve Nelson, Fred Sanders, Jeff Peters, Russ
Why Fusebox? What Is Fusebox? Structured architecture - scalability, maintainability, modularity Facilitates team development Self-documents your application Allows repeatability Large community Proven but evolving Community-driven Extensible - Fusebox for PHP, JSP, ASP Quick to learn Free
General Fusebox Theory Index.cfm is controller - all interaction goes through the Fusebox via Fuseactions Multiple index.cfms for sections of the site, called circuits Root index.cfm handles global variables, root requests Index.cfm acts via cfcase, including files (fuses) and logic If a circuit blows up, the entire site is not blacked out Electrical fuse box metaphor Circuits are modular, thus reusable New Extended Fusebox (Hal-style) standard calls for no home application: All circuits standalone with individual cfapplication tags and no global variable dependencies – cfparam all vars All circuit index.cfms are cfincluded, not
First Steps (Pre-Coding) 1. Produce a quality specification
Nothing Fusebox specific here Be on the lookout for Secretagents.com spec tool
2. Use fUseML or another modeling tool to make the design including directory structure
fUseML is derived from the UML Build design taking index.cfm interaction (Fuseactions) into account
3. Create stringent Fusedocs for all fuses
Fuses should not be dependant on any variables not explicitly stated Make assertions if necessary
Creating A Fusebox Application
Create the index.cfm files Create Fuseactions in index.cfm Create Fusedocs for fuses Write fuses Stand back and marvel
Create the Index.cfm Files Every directory (circuit application) has one index.cfm file Index.cfm controls all the Fuseactions of that circuit application It is the Fusebox All links and form submissions go to the index.cfm It is a single cfswitch statement with multiple cfcase statements Each cfcase is a different Fuseaction
The Fusebox Code
More on the custom tag later…
Model-View-Controller Approach Request
This is Meant to Be Just text That isn’t Clear. I hope It works the Way I want It to.
cf_do_logic
(model)
Fusebox (controller) This is Meant to Be Just text That isn’t Clear. I hope It works the Way I want It to.
dsp_UserLogin.cfm
HTML Returned
(view)
Create the Fuseactions A Fuseaction may cfinclude .htm/.cfm; cfmodule; cflocation; contain limited cfml A Fuseaction may NOT display anything to the browser or contain “open”
Determine what steps are needed to complete each Fuseaction Add those steps inside each cfcase statement
File Naming Conventions (Fuses) app_globals.cfm – File defines variables, instantiates application request.mainDSN, request.webroot, request.mypath
dsp_filename.cfm - Display file
Only file that contains HTML or any output to browser
act_filename.cfm - Action file
Only file allowed to perform actions on the database – updates, inserts, deletes, selects allowed, but only in conjunction with action
qry_filename.cfm - Query file
Extremely modular file can be called “willy-nilly” throughout application, performs selects on database
Fusedoc Documentation Standard A Fusedoc outlines responsibilities, customizations, and expectations of fuses, and is unique to each fuse No fuse can assume the existence of any variable unless it is noted in the Fusedoc for that fuse Once completed, a Fusedoc should provide all the information needed to code the fuse – no interaction with application architects or previous specifications should be needed A Fusecard contains the following elements: Name of the file Responsibilities (non-technical, plain English, derived from the application design/fUseML) Author / coder Variables list (incoming, outgoing, and persistent)
Fusedoc Legend --> <-<-> ++>
explicitly passed incoming parameter explicitly passed outgoing parameter pass-thru parameter (unchanged) existing persistent parameter (session, client, etc.) <++ created persistent parameter +++ included file [parameter] brackets indicates optional Examples: --> CurrentUser: a WDDX STRUCTURE <-- [badLogin]: optional, a STRING <++ Session.ColorChoice: a STRING (Red|Blue) <-> UserID: an INTEGER +++ myGlobals.cfm
Create the Necessary Fuses Because the Fusedocs are so carefully built, and the design so thoroughly thought out, individual fuses can be “farmed out” for coding Remember – all links and form actions go to index.cfm, specifying which Fuseaction to perform; never to the specific dsp or act files. Javascript:window.location=‘index.cfm?fuseaction=Buy’
Related Documents
Fuse Box
May 2020 10
Fuse
November 2019 25
Fuse Box Toyota Corolla E100.pdf
June 2020 6
Fuse Info
October 2019 18
Fuse 1
October 2019 18
Fuse Clip
May 2020 3More Documents from ""
Javascript
May 2020 19
Database Design: Dick Steflik
May 2020 26
Ch8 Structures
April 2020 24
The Future Of Tcp/ip (ipv6)
May 2020 24
Ch4 Functions
April 2020 24