It'd be optimal if you where using the PageContext continously (ie client-side) but from what i have read and heard, the objects are destroyed after they are instantiated at runtime.
 
Having said that, it'd probably best to kill them if you have them instantiated in a session.scope etc? Not sure on what impact it may or may not have on the serverside. I know in some languages you can't actually kill the object in that you can set it to null, but say in languages like DHTML / Actionscript still reserves memory for that object even though you no longer use its full memory capacity.. hence memory leaks are the bain of your existance.
 
Scott
 
 
"Taco Fleur" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]...
Is it recommended like in VB to destroy an object once you are done with it?
i.e. objThis = false; ????
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]

MX Downunder AsiaPac DevCon - http://mxdu.com/

Reply via email to