If I was designing the site, I'd move all variables that had to be unique to each site into session variables. This way I wouldn't have to worry about my application variables getting mixed up between sites, especially with all the server wide includes that probably depend on and make calls to the application scope. Which is what I suspect is happening. Each user's session would then retain the information about the specific site they are on.
HTH, Joe Kelly On 8/16/05, Kevin Fricke <[EMAIL PROTECTED]> wrote: > > OK, let me tell you a bit more about what we are doing. I am sure that the > design of the application is the cause...I just don't know where to start. > > We have a site that processes online reservations. > > We also have hundreds of "clone" sites which we market to get the bookings. > Each clone is its own site. Therefore, we have each one set up with it's > own application name and several application variables. Then each page > deeper in the site pulls several pages from includes. Each include is > pulling data from the database. This way if we change a page we only have > to change it in one place. > > Make sense? > > Should we be using something other than application variables. As far as I > know we are not caching any queries. > > Thoughts? > > Kevin -- Thanks, Joe Kelly ---------------------------------------------------------- To post, send email to [email protected] To unsubscribe: http://www.dfwcfug.org/form_MemberUnsubscribe.cfm To subscribe: http://www.dfwcfug.org/form_MemberRegistration.cfm
