Chris Gray wrote: > > A caveat about the REQUEST.set method: > > There is a memory leak associated with this technique. Use it as > sparingly as possible. I don't think your memory leak is associated with doing a REQUEST.set, unless you're doing something that ends up doing: REQUEST.set(xxx,REQUEST) ...in some way, in which case it's an application problem ;-) cheers, Chris