Casey Duncan wrote:

Hi Phill,

Thanks for the feedback. As for the REQUEST vs. RESPONSE usage, the latter can't be used to store values and is really there as a way to communicate to the browser. The former is used pretty regularly to store scratch variables already.

Looks like the set() method has been removed from 2.3. I remember using it many a time in 2.2 and 2.1 to do this kind of thing though. RESPONSE.set() worked in the same way as REQUEST.set() but without messing REQUEST up (which in the same light is just a way for the browser to communicate with you) Looks like RESPONSE.__setitem__ maps things directly to the setHeader() method. <snip>

A possible solution to this is for the method to push an empty scratch namespace for itself when it starts and pop it when it finishes. Then the eval tag can just use this namespace to store variables. I considered that too complex for my first release, but I certainly will reconsider it for future ones.

This does sound like the way to go. Phill