Yup, if there isn't a way to make application scope stay in its playpen, then I'll have to rewrite to domain scope. Domain just offers more possible conflicts with other variables in the domain. For instance, my forum runs an array of "who is here" conveniently named @@application$whoishere
Buddy writes a chat application with @@application$whoishere doing the same thing for the chat application Then to go to domain scope, a little more coordination and record-keeping is in order to make sure that variable names don't step on each other and are more like: @@domain$chat_whoishere and @@domain$forum_whoishere On 11/29/04 9:48 AM, "Bill Conlon" <[EMAIL PROTECTED]> wrote: > Roland, > > just want to encourage you to consider domain scope variables. Some > advantages: > 1. it's easier to manage updates > 2. less server memory use, since they can all get cached > > > Domain var initialization is tricky though. I have an init.taf that > sets them up for each domain, by using CGIPARAM to select all needed > parameters based on the domain name. But startupurl doesn't work for > this, so I do it in my witango startup shell script. > > On Monday, November 29, 2004, at 09:35 AM, Roland Dumas wrote: > >> At this point, you've created the same workaround I ended up with. >> >> Instead of all forum applications living in the /forum/ directory of >> their >> respective virtual hosts, they must live in /forum_a/ , /forum_b/ etc, >> and a >> corresponding application set up in the applications.ini file >> >> With every instance of /forum/ changed to <@APPPATH> in apps and >> includes, >> it will work around the malfunctioning application scope. >> >> I was hoping that someone would slap me on the wrist and say to add a >> certain line to the applications.ini file and all would behave as it is >> expected to.... >> >> >> >> On 11/29/04 9:28 AM, "Alan Wolfe" <[EMAIL PROTECTED]> wrote: >> >>> well, one mothod might be this.. >>> >>> lets say you have one in a folder named "a" and another one in another >>> folder named "b". >>> >>> if you extract the subfolder name of "a" and "b" from something like >>> <@appfile> and assign it to a variable (for example >>> local$subdirectory) you >>> could use variables like this.. >>> >>> <@assign scope=domain name="<@var local$subdirectory>UserCount"> >>> >>> that would create aUserCount and bUserCount in the respective >>> subfolders >>> which would seperate the applications since they are different >>> variable >>> names. >>> >>> Not the most elegant solution and would take some code changing but >>> if there >>> is no elegant solution, it might work out pretty good (: >>> >>> ----- Original Message ----- >>> From: "Roland Dumas" <[EMAIL PROTECTED]> >>> To: <[EMAIL PROTECTED]> >>> Sent: Monday, November 29, 2004 9:18 AM >>> Subject: Re: Witango-Talk: Same application name, different domains: >>> worka >>> round >>> >>> >>>> Separate tafs, etc. Copy the whole folder into each domain. >>>> >>>> I understand, but not quite there with your strategy. In a perfect >>>> world, >>>> one copy of the tafs could be used with many sites, each with its own >>>> formatting and database. I'll get there eventually, but right now, >>>> just >>> want >>>> to clone a directory, move to a new site, and have the application >>>> scope >>>> variables in that new directory not comingle with the same named >>> application >>>> scope variables in other domains. >>>> >>>> >>>> On 11/29/04 9:01 AM, "Fogelson, Steve" >>>> <[EMAIL PROTECTED]> wrote: >>>> >>>>> Roland, >>>>> >>>>> Are you using separate tafs, tcfs and tmls for each domain or are >>>>> you >>> using >>>>> one "copy" of them for all the domains. >>>>> >>>>> If you are using one "copy", why not determine the domain when a >>>>> client >>> hits >>>>> the site and assign a site id and use it for accessing custom scoped >>>>> variables that define the database to access, site template, css, >>> scripts, >>>>> etc. >>>>> >>>>> A number of developers in this group use this with great success. >>>>> >>>>> Steve Fogelson >>>>> Internet Commerce Solutions >>>>> >>>>> -----Original Message----- >>>>> From: Roland Dumas [mailto:[EMAIL PROTECTED] >>>>> Sent: Monday, November 29, 2004 10:46 AM >>>>> To: [EMAIL PROTECTED] >>>>> Subject: Re: Witango-Talk: Same application name, different domains: >>>>> workaround >>>>> >>>>> >>>>> >>>>> I intended to create an application /forum/ that could be dropped >>>>> into >>> many >>>>> domains on the same server. Each would have its own application >>>>> scope >>>>> variables. >>>>> >>>>> The experience is that application scope leaks across domains, such >>>>> that >>> an >>>>> application in one domain shares variables with the same >>>>> application in >>> all >>>>> domains. That's the described behavior of custom scopes, not >>>>> application >>>>> scope. >>>>> >>>>> After walking through the rather terse documentation and the mailing >>> list >>>>> archives, I couldn't find a hint as to how to keep application scope >>>>> variables within each domain, so I had to create a workaround: >>>>> >>>>> - change all path designations in the application from /forum/ to >>> <@APPPATH> >>>>> - create an application for each domain, with path definitions being >>>>> /forum_1/ , /forum_2/ etc >>>>> - in each domain, not use a directory that is associated with an >>> application >>>>> in another domain. >>>>> >>>>> Clarification as to what should be the behavior of app scope >>>>> variables >>> is >>>>> requested. >>>>> >>>>> >>>>> ____________________________________________________________________ >>>>> ____ >>>>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >>>>> ____________________________________________________________________ >>>>> ____ >>>>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >>>>> >>>> >>>> >>>> ----------------------------------------- >>>> Roland Dumas >>>> Roberts Information Services >>>> 310 W. Bellevue Avenue >>>> San Mateo CA 94402 >>>> 650-347-1373 >>>> 415-412-9300 (cell) >>>> [EMAIL PROTECTED] >>>> SMS: http://new.servqual.com/html/sms.tml >>>> >>>> >>>> _____________________________________________________________________ >>>> ___ >>>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >>> >>> ______________________________________________________________________ >>> __ >>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >>> >> >> >> ----------------------------------------- >> Roland Dumas >> Roberts Information Services >> 310 W. Bellevue Avenue >> San Mateo CA 94402 >> 650-347-1373 >> 415-412-9300 (cell) >> [EMAIL PROTECTED] >> SMS: http://new.servqual.com/html/sms.tml >> >> >> _______________________________________________________________________ >> _ >> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >> > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > ----------------------------------------- Roland Dumas Roberts Information Services 310 W. Bellevue Avenue San Mateo CA 94402 650-347-1373 415-412-9300 (cell) [EMAIL PROTECTED] SMS: http://new.servqual.com/html/sms.tml ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
