The fusebox ontwikkelmethode is nu van CFML naar PHP gepoort.
Ik werk zelf in CF en heb weinig ervaring met php, maar kijk er eens naar.
Meer info te vinden op: http://bombusbee.com (fusePHP)
En de officiële fusebox site: http://www.fusebox.org
Introduction
Fusebox is a development methodology for web applications. Its name derives from its basic premise: a well-designed application should be similar to the fusebox in a house. In a fusebox, if one fuse is blown, the rest of the fuses continue to work. Each fuse has its own defined job, and Fuse A does its job without any help from Fuses B, C, or D. Similarly, in a Fusebox application, if one section of the application "breaks", the rest of the application should continue to work.
Fuseactions
In a Fusebox application, every action that an application must handle is referred to as a Fuseaction. For example, an e-commerce application would include the following possible Fuseactions:
viewCart
viewCatalog
addItem
checkOut
Fuses
To perform each Fuseaction, a Fusebox application uses a series of ColdFusion pages. Each page is referred to as a Fuse. To perform the Fuseaction 'viewCart' mentioned above, the user's cart must first be queried and then the results must be displayed. Therefore, the Fuses called for the Fuseaction viewCart would be:
qryCart.cfm
dspCart.cfm
This brings us to a discussion of the possible types of fuses.
Types of fuses
Fuses can be grouped into a finite number of types. The four most common are:
Display fuses, prefixed with dsp, which are used to show information to the user.
Select Query fuses, prefixed with qry, which contain SELECT queries
Action Query fuses, prefixed with act, which contain INSERT, UPDATE, DELETE or other action queries.
Location fuses, prefixed with url, which redirect the application to a new URL.
Ik werk zelf in CF en heb weinig ervaring met php, maar kijk er eens naar.
Meer info te vinden op: http://bombusbee.com (fusePHP)
En de officiële fusebox site: http://www.fusebox.org
Introduction
Fusebox is a development methodology for web applications. Its name derives from its basic premise: a well-designed application should be similar to the fusebox in a house. In a fusebox, if one fuse is blown, the rest of the fuses continue to work. Each fuse has its own defined job, and Fuse A does its job without any help from Fuses B, C, or D. Similarly, in a Fusebox application, if one section of the application "breaks", the rest of the application should continue to work.
Fuseactions
In a Fusebox application, every action that an application must handle is referred to as a Fuseaction. For example, an e-commerce application would include the following possible Fuseactions:
viewCart
viewCatalog
addItem
checkOut
Fuses
To perform each Fuseaction, a Fusebox application uses a series of ColdFusion pages. Each page is referred to as a Fuse. To perform the Fuseaction 'viewCart' mentioned above, the user's cart must first be queried and then the results must be displayed. Therefore, the Fuses called for the Fuseaction viewCart would be:
qryCart.cfm
dspCart.cfm
This brings us to a discussion of the possible types of fuses.
Types of fuses
Fuses can be grouped into a finite number of types. The four most common are:
Display fuses, prefixed with dsp, which are used to show information to the user.
Select Query fuses, prefixed with qry, which contain SELECT queries
Action Query fuses, prefixed with act, which contain INSERT, UPDATE, DELETE or other action queries.
Location fuses, prefixed with url, which redirect the application to a new URL.
).