Hi chz,
 
In Fusebox, and particularly in FB3, all input parameters (form, url and attributes) are copied to the standard CF scope called "attributes".  After that, the form and url scopes are hardly ever referenced.  This means that your code normally won't know or care where the inputs came from.  This is a great aid to code re-use, meaning that your code can be used in all kinds of circumstances, eg the code that updates data in a database record could receive the data from an HTML form, or passed as URL variables after some data validation, or the data could even be passed as attributes in a cfmodule call.  You code won't care.
 
So in general, when you see something called "attributes.xxx" in a Fusebox app, it's probably user input.
 
Request-scoped variables, on the other hand, are global to any given HTTP request, and are thus available to all of your code, including custom tags and recursive cfmodule calls.  In Fusebox, request-scope is often used for holding fundamental application constants (like the title of the app, or the datsource name).  There is also some thought that request-scope is less susceptible to user "tainting".  Nevertheless, most of the usual warnings about using global variables apply to request-scope.  Their use is often seen to violate the principles of encapsulation, etc.
 
Does that make any sense?
LeeBB

----- Original Message -----

 
I'm about to build my first fusebox3 application. Since I never did
anything with fusebox and I didn't code in ColdFusion for some years I
feel like I have to start with very small steps again.

In looking at the code of fbOpenForums (which I feel is an excellent
example to teach me some fusebox) I see act_login.cfm setting variables
like "attributes.loginMsg".

Can someone explain to me the meaning of attributes?

I think it has something to do with the scope af the variable but is the
use of it something fusebox specific or do I miss some basics here?
Propably in the same category belongs the question about
request.queryPath.
==^================================================================
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