Well generally you are right, but who allways writes variables.name or
something like that. Even if you have defined the scope the checks still
have to be done and the engine has to check wether it is a valid scope
(or a structure or something else) or not. By configuring the scope
cascading to "strict" (see below), railo knows, that a variable without
a scope can only be found in the variables or arguments scope. And
please recall that in CFMX something like this (might be stupid) still
works:
<cfset test = caller.name> If in the "caller" scope there is a form
variable called "name" CFMX will find this variable, allthough the form
scope is present in the current template too. You could also write
<cfset test = caller.form.name>
Well exactly spoken in railo you can configure scope cascading in the
following way:
Extract of the railo.xml:
<!--
scope configuration:
cascading (expanding of undefined scope)
- strict (argument,variables)
- small (argument,variables,cgi,url,form)
- standart
(argument,variables,cgi,url,form,cookie)
cascade-to-resultset: yes|no
when set to yes, railo allows inside a <cfoutput
query="queryname"> and <cfloop query="queryname"> to call columns of the
resultset implicitly
merge-url-form:yes|no
when set to yes all form and url variables are
merged into both scopes
-->
<scope
cascading="standart"
cascade-to-resultset="yes"
merge-url-form="no">
- Gert -
-----Ursprüngliche Nachricht-----
Von: Jordan Michaels [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 5. November 2004 01:20
An: CF-Talk
Betreff: Re: Bluedragon Server
Intriguing. I was always under the impression that if you defined the
scope in the first place, the same kind of performance increase would
occur? Is that not what happens?
Thanks! Keep up the good work!
-Jordan
Gert Franz wrote:
>hi there,
>
>just take a look at the performance tests we did with railo alfa 4 in
>comparison to cfmx.
>http://www.railo.ch/en/documentation/index.cfm?treeID=30
>We have a lot of improvements and in railo and no big limitations
>(except for the couple of tags and functions that we still have to
>implement). Take the scope cascading for example. By turning it off you
>can boost the performance of railo greatly. Scope cascading allows you
>to implicitly reference variables. For example you can write the
>statement <cfset test = Name>. The variable Name has no Scope-Qualifier
>so Railo normaly checks the usual scopes (in a predefined order
>[variables, current query, form, url a.s.o.]) to find it. You can turn
>this behaviour off so that you have to write <cfset test = url.Name>.
>This leads to a large improvement in execution-speed. And adding to
>this the code can be easier read. Of course this is a (configurable)
>limitation, but with the advantages you get, you won't consider it to
>be a limitation.
>
>Check out www.railo.com for updates.
>
>We plan to release Railo Beta in the first quarter of 2005.
>
><cfregards from="Gert Franz" who="railo developer"
>location="switzerland" respondto="[EMAIL PROTECTED]">
>
>
--
Warm regards,
Jordan Michaels
Vivio Technologies
http://www.viviotech.net/
[EMAIL PROTECTED]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Special thanks to the CF Community Suite Gold Sponsor - CFHosting.net
http://www.cfhosting.net
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:183436
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
