The default domain key in Tango for the Mac is the base URL or IP address (retrieved using <@CGIPARAM SERVER_NAME>. So www.mydomain.com/my.taf will return a different variable of the same name than 203.111.222.333/my.taf. It is possible to set a different value for the domain key in the domainScopeKey system variable - see how to do this in the Meta Tags & Config Variables pdf.
So your problem is either that you are accessing the same taf using the same domain key (ie the ip address or base url is the same) or the domain key has been changed and wither isn't picking up the domain properly or you need to re-think what domain key you use. Not that it is important to user the <@LITERAL> tag when assigning domain keys to the domainScopeKey system variable. Also, in response to Jon's statement about setting up different methods under one vitual domain using IIS, this can actually be achieved by incorporating several different domain names and ip addresses under the one "Tango domain". Either edit the config file directly or use the config.taf admin applicaiont file to specify which domains should be aprt of the Tango domain - you can set up multiple Tango domains. One last area you should check is that the variableTimeout system variable is set to a long enough time - otherwise your domain scopes can time out too quickly. As a general thing, because I have quite a number of tafs in different web sites on the one server, I simply name the application files differently and this saves me having to deal with specifying domain keys in any great detail. Hope this helps Garth At 12:43 25/09/02, you wrote: >Wayne, > >I would say this is likely to be a problem with the Web Server, rather than >Tango. I'm a Windows-kinda-guy, so can't comment on any aspect of >WebStar... > >Here's how it *should* work... > >On Windows, the way in which domain-scope variables is handled is partly due >to the Web Server (I use IIS) and partly down to the configuration of Tango. >For example, it is possible to access the same virtual server using multiple >domains/subdomains, for example, www.mydomain.com; mydomain.com; >foo.mydomain.com; 192.168.0.1; etc. You configure the Web Server to host >all of those as a single virtual server. > >In Tango, the default behaviour is to allocate domain-scope variables to >whatever domain the site was accessed from. In the example above, you'd >actually get 4 sets of unique domain-scope variables. You use the >domains.ini (on Windows) to tell Tango that all the variations are the same >"Tango Domain" with an entry something like this: > >[Domains] >mydomain.com= > >[mydomain.com] >1=www.mydomain.com >2=mydomain.com >3=foo.mydomain.com >4=192.168.0.1 > >This forces all the different possible URLs for the same site to be >'grouped' together and share domain-scope variables. > >Obviously, what you're seeing is a separate problem, but I thought this >might invoke some thought as to where the WebStar problem lies... > >Regards, >Jon > > > >-----Original Message----- >From: Wayne Irvine [mailto:[EMAIL PROTECTED]] >Sent: 25 September 2002 11:57 >To: Multiple recipients of list witango-talk >Subject: Witango-Talk: Arrays of scope domain don't behave > > >Does anyone want to make comment on this? > >____________________________________________ > >I'm sure this has been covered and I was playing hookey that day but I have >just discovered that arrays of scope 'domain' don't seem to want to behave. > >If I assign an array in one domain it can be seen in another on the same >server. > >I'm using Welcome for virtual hosting, WebStar 4.4 on Mac OS9.1 on a G4. >It's Tango 2000 with the last SP Pervasive ($#&%$) released. > >Is this a known problem? >Is there a solution? > >Wayne Irvine > > Byte Services Pty Ltd > http://www.byteserve.com.au/ > [EMAIL PROTECTED] > Ph 02 9960 6099 Mob 0409 960 609 Fax 02 9960 6088 > >________________________________________________________________________ >TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body >________________________________________________________________________ >TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
