Think of it this way: Most tags will evaluate the same in a tcf as in a taf. Meaning that @DOMAIN will respond the same value, so theoretically any variables attached to that domain will also carry properly.
Application scopes are 'larger' than domain scopes, so it's proper for one application to have more than one domain. In fact, it's a little better to think of the application scope as a subset of the system scope, rather than a superset of domains. It might also help to think about this situation in a custom scope. If you put your TCF in the variable my_tcfs$subroutine (custom scope of 'my_tcfs'), then calling a method within would apply to each user's user, domain, and application scope as it exists at the time of the call. Data wouldn't cross, and your domain-based variables would apply to the user's domain. Since the custom scope sits outside of the whole tree and is explicitly accessed, it has no allegiance. Robert -----Original Message----- From: Bill Conlon [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 29, 2004 4:19 PM To: [email protected] Subject: Re: Witango-Talk: TCF questions Not what I'm doing. In fact, I don't have any domains defined. Instead I initialize domain scope variables each domain using an appfile. Each domain these is a virtual host that points to the same directory on the web server. It is this directory that is defined in applications.ini But for the TCF in application scope (so all domains using the application share a single TCF object) I was curious about the scope chain. This only came up because I was looking at converting a working appfile used as a subroutine into a call method. I wanted to just drag the working guts over to a method. But some input parameters to the appfile subroutine were domain scope, some user scope. I wasn't sure how an appscope TCF would figure out which domain scope to use. Stefan is right about programming practice, but I was curious about getting an existing interface to work in a method. On Wednesday, December 29, 2004, at 12:34 PM, Roland Dumas wrote: > This goes back to setting up applications by defining domains and > applications, which took me some time to read the omitted > documentation. > > If you do it right, then app scope is a subset of its domain. > Therefore your > various domains would have to instantiate the TCF in their respective > applications and that a call method would know what domain applies. > > > On 12/29/04 12:11 PM, "Bill Conlon" <[EMAIL PROTECTED]> wrote: > >> I have a TCF in application scope. >> >> I have multiple domains that use the the TCF. >> >> When invoked, I take it that a call method would not know which domain >> applies, so any domain variables that it would use should be passed as >> arguments, correct? >> >> ______________________________________________________________________ >> __ >> 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 ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
