From: Willem J. P. <wpa...@ma...> - 2008-07-25 09:12:44
|
On Thu, Jul 24, 2008 at 02:58:47PM -0700, Marzo Junior wrote: > You can have a static usecode variable pointing to an object which > is cached out; the ID would then be invalidated, but the variable > would still refer to it. Could you explain the exact requirements of the static usecode variables? I'm afraid I have forgotten the specifics. Specifically: Should the object still be accessible when it is cached out? If no, should it become accessible again if it is later re-cached in? -Willem Jan |