Technically, there is no connection between the user session and the local scope. However, local/request variables are locked to the currently executing request, which is also their lifetime. Since a request can only be accessed by one user session – the requestor – it has the effect that each local/request scope belongs to just one user.
Robert From: WebDude [mailto:webd...@cipromo.com] Sent: Tuesday, November 29, 2011 3:22 PM To: Witango-Talk@witango.com Subject: RE: Witango-Talk: Scoping Variables Another question and maybe a stupid one. Are variables scoped as local local to the user scope? I would assume so. In other words, a locally scoped variable is local for that particular user, right? _____ From: Wayne Irvine [mailto:wa...@byteserve.com.au] Sent: Monday, November 21, 2011 4:15 PM To: Witango-Talk@witango.com Subject: Re: Witango-Talk: Scoping Variables I go through this often with code written for Tango 3/2000/5. As long as you change Terascripts default scope to user it should all work fine. But I prefer to have request as my default scope and specify scopes specifically in my code. This means a lot of work, but also a chance to review the code I am upgrading. Some of it was written over a decade ago. Wayne Irvine On 22/11/2011, at 6:57 AM, Tom Ferguson wrote: Not to hijack WebDude's thread, but I'll be doing the very same thing soon, going from 4.5 to TeraScribe. I have no scopes specified either. What happens if I leave the scopes as is? Thanks! _____ From: WebDude [mailto:webd...@cipromo.com] Sent: Monday, November 21, 2011 1:18 PM To: Witango-Talk@witango.com Subject: Witango-Talk: Scoping Variables Hi Folks, I am currently preparing to upgrade from version 4, probably to version 6 and then up to Terascribe. I remember that syntax and scoping of variables have changed. I am trying to prepare as much of the old files as possible before upgrading. I will probabaly have more questions to come, but I am going to take this a step at a time. First question is concerning scoping variables. Presently, almost all variables are not scoped so I am going through the ardious process of straightening these out. A few questions, if you don't mind... I would assume that you need to scope all <@ASSIGNs Most of the applications have no scope assigned to them presently. Of course, the default for this is "user" in the version I am using, but I am going to go through each assign and scope it appropriately. Almost all are goinmg to be scoped as user, but I have a few that can be scoped as local. Whenever calling on the variable, such as <@VAR blah> I am also going to assume these need to be scoped as well, as is <@VAR blah scope "user"> Do I need to scope any <@PURGE variables? When calling a local variable, should these be scoped as well? i.e. <@VAR blah scope "local"> What exactly is the request scope? This will be for futue reference. It appears to be the same as the local scope. When I upgrade, will I need to change all local scopes to request scope? Is this just a neam change to avoid confusion Thanks for any help! _____ To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body. _____ To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body. _____ To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body. _____ To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body.
