Title: Re: Witango-Talk: �'data' system variable
Yeah, you are correct.
I wanted to be sure so I created 2 tafs
 
testLocal1.taf
-------------------
<@ASSIGN NAME="TestLocal" VALUE="local" SCOPE="local">
<@ASSIGN NAME="TestRequest" VALUE="request" SCOPE="request">
<@ASSIGN NAME="TestUser" VALUE="User" SCOPE="user">
<A HREF="<@CGI>TestLocal2.taf?<@USERREFERENCEARGUMENT>">Go to 2</A>
 
And
testLocal2.taf
-------------------
@@local$TestLocal<br>
@@request$TestRequest<br>
@@user$TestUser<br>
 
the result was only the
@@user$TestUser value survived
 
After I Sent the email I realized that it would be crazy if that were the case
:-b
 

Ben Johansen - http://www.pcforge.com
Authorized WiTango Reseller
http://www.pcforge.com/WitangoGoodies.htm
latest beta downloads @ http://www.witango.ws 


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Stefan Gonick
Sent: Monday, November 11, 2002 7:58 PM
To: Multiple recipients of list witango-talk
Subject: Re: Witango-Talk: 'data' system variable

on 11/11/02 7:13 PM, Ben Johansen at [EMAIL PROTECTED] wrote:

Have you tried using the REQUEST Scope (the new local scope)
@@request$data
In version 5 local scope becomes a custom scope and you have to purge it yourself so it wont step on itself
if you know what I mean ;-)

Ben Johansen - http://www.pcforge.com <http://www.pcforge.com/>
Authorized WiTango Reseller
http://www.pcforge.com/WitangoGoodies.htm
latest beta downloads @ http://www.witango.ws <http://www.witango.ws/>   
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dave Machin
Sent: Monday, November 11, 2002 5:24 PM
To: Multiple recipients of list witango-talk
Subject: Witango-Talk: 'data' system variable

Is there a system variable called @@data in WiTango 5?  I have code that was working on the previous version, but everywhere I've referenced a local scope variable 'data' the code doesn't work.  When I renamed the variable it was OK...

Dave Machin



I don't think that local scope became a custom scope in W5. A custom
scope behaves totally differently than local or request scope does.
It persists across requests. I was under the impression that local
scope is just an "alias" for request scope in W5.

Stefan

Reply via email to