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
