No it is one application that does the work, think about it for a minute and you'll see what I mean by that.
Why not, because you are using one application name. Hence it is one application. Don't get me wrong there is nothing wrong with what you have described, I have done it many times where I had core code for portals that ran through the one application. All I am saying is that the application is sharing all the code, hence it is one application that pretends to many websites. As far as I am concerned I will always treat it as one app, and not 2 if there are 2 sites. Hope that makes sense:-) -----Original Message----- From: S. Isaac Dealey [mailto:[EMAIL PROTECTED]] Sent: Thursday, 27 June 2002 11:46 AM To: CF-Talk Subject: RE: What is the best variable scope? > Ok that goes without saying, but in hindsight this is one > application pretending to be many It's not really pretending... It is actually doing the job -- the structure of the application helps to prevent namespace conflicts by isolating most of the data elements across different websites by datasource id's (they all share a datasource as well)... > and should not be used as an example of sharing > application variables across websites (applications). Why not? It's not necessarily a freak or isolated incident... I could see plenty of benefits by doing something similar with the structure of other sites / applications not on my CMS ... I was merely pointing out that when you say "You seem to think application is across websites, this is not true." -- it's really a non-sequitur -- websites or domains and application vars have zero to do with one another... Isaac www.turnkey.to 954-776-0046 ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
