That is a different approach... thanks for the concept. I have said many
times... that liberty should be allowed if programs perform for the
requirements and the code is easy to follow. Interesting concept Sean...
KUDOS!
John
The other thing you could do is have your application start/end
methods defined in a tree of CFCs outside the webroot and then just
have each Application.cfc extend the appropriate CFC from the tree:
components/
BaseApplication.cfc
app1/
App1Application.cfc (extends BaseApplication)
app2
App2Application.cfc (extends BaseApplication)
webroot/
Application.cfc (extends BaseApplication)
app1/
Application.cfc (extends app1.App1Application)
app2/
Application.cfc (extends app2.App2Application)
You Application.cfc object would be completely empty - all of the
logic would be in the Base / App1 / App2 versions.
Not sure whether I think that's good practice or not...
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
