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
