It's about time ;-))
I know a few people who were anxious to have a look at it..
I only had a look at the application.cfm so far, and there is only one thing
that I noticed at this stage, there is no password required to re-initialize
the application variables.
I reckon it will take a while to initialize the application, thus if someone
wants to bring the app down all you need to do is send an XXXX requests with
"appinit" in the url and up goes the CPU.
I use
<!--------------------------------------------------------------------------
--------------------
Store commonly used components/objects in the application scope.
Or re-initialize components.
----------------------------------------------------------------------------
-------------------->
<cfif NOT structKeyExists(server, "component") OR ((url.componentInitialize
OR url.initialize) AND url.password IS "appinit999")>
<cfinclude template="application/app_component.cfm">
</cfif>
<!--------------------------------------------------------------------------
--------------------
Make sure the meta structure exists in the application scope.
----------------------------------------------------------------------------
-------------------->
<cfif NOT structKeyExists(application, "meta") OR ((url.metaInitialize OR
url.initialize) AND url.password IS "appinit999")>
<cfset application.meta = structNew()>
</cfif>
<!--------------------------------------------------------------------------
--------------------
Store all page meta data in the application scope.
----------------------------------------------------------------------------
-------------------->
<cfif NOT structKeyExists(application.meta, "page") OR ((url.pageInitialize
OR url.initialize) AND url.password IS "appinit999")>
<cfinclude template="application/app_page.cfm">
..............
And of course its up to the people to change the password "appinit999" to
something else with every new application.
On most applications, I know its still a guessing work as to what the
variable name is to re-initialize the application, but with an open
framework it is known and it will create a hazard, in my eyes anyway.
Just a thought ;-))
Taco Fleur
Blog http://www.tacofleur.com/index/blog/
Methodology http://www.tacofleur.com/index/methodology/
Tell me and I will forget
Show me and I will remember
Teach me and I will learn
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Scott Barnes
> Sent: Monday, 1 March 2004 3:25 PM
> To: CFAussie Mailing List
> Subject: [cfaussie] BatFink Released...
>
>
>
> Heyas
>
> As most of you probably know, we here up Tourism Queensland eCommerce
> Dept, have been using a framework called "BatFink".
>
> Spike, the beer-o-matic himself is the core brains behind this puppy,
> but none the less, most of us understand it, but yeah,
> download it, play
> with it, tell us it sux, tell us it rox, either way we'd love
> to see how
> your initial reaction to it is.
>
http://www.mossyblog.com/batfink10.zip
Its a self-documenting WIKI (well not as hardcore on the docs part, but
its enough to get you started). Its based on the MVP pattern aswell.
Now go play, thats an order... now MUSH MAGGOTS!
--
Regards,
Scott Barnes
-
http://www.mossyblog.com
http://www.bestrates.com.au
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To
unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004
