Hi, for these concerns I always refresh my memory going to this vid:

InterSystems Webinar: Configuring a Web Server for IIS for Better Performance and Security 

Some key URL's you may find helpful too (find the newer version according to your IRIS version):

CSP Gateway Configuration Guide:
Web Servers for Microsoft Windows
How to Set Up SSL on IIS 7

Ok so, to summarize the thread:

1.- Work with variable table names.
2.- Being able to 'see'/'use' them (i.e. the evenTotal count)
3.- Not having the variables loaded in memory after method execution.

In '' you can have all 3. In '.cls' you can only have 1 and 2, waiving point 3. 

Options in '.cls' from better to worse in my opinion are:

a. The cleanest option I've seen is @Jose Tomas Salvador version. This option still doesn't have the point 3 but you can kill the variables before leaving the method.

b. Before 'Jose Tomas version' my choice was adding the variables to public list, and trying to kill them before leaving the method. Although it breaks the not knowing the names thing.

c. Using percent variables (obscure, and also my colleages don't know well percent vars, so risky too)

d. Set ProcedureBlock=0 (worst choice in my opinion as it makes visible all variables)

Thank you very much for your help as I was a bit anxious with this thing thinking there was a better option and I was too clumsy to find it.

Thanks for the reply. I've tried that too, but if I set the ProcedureBlock to 0, all the variables stay loaded in memory after the method execution, which is worse than having only the ones used inside the indirection.

Is it a dead end? There is no chance to have it working?

I read about $XECUTE accepting parameters. I tried some aproaches without good results. Could it work using that, @Robert Cemper ?

Also, thanks a lot for the link, it's a very interesting post. 

Arturo has no followers yet.
Arturo has not followed anybody yet.
Global Masters badges: