Loading Dom nodes into Memory - best practise

Hi,

I'm working on a project where I'm manipulating elements on the page
in response to user input. I've created objects which load the
elements to be manipulated as member variables on page load. The
objects provide an interface to manipulate the elements they are
responsible for. The event handlers use this interface.

This approach makes event handling very responsive, as no dom
traversal is needed when the event fires. (Or very little - sometimes
I use firstChild or previousSibling.)

I'm wondering if there are any problems caused by loading dom nodes
into browser memory and leaving them there for as long as the page is
open in the user's browser. I'm loading about 20-50 nodes like this.
Leaving the page open in Firefox and IE for several hours doesn't seem
to cause any problems - but I have plenty of memory.

regards,
Richard


------------------------ Yahoo! Groups Sponsor --------------------~--> 
Home is just a click away.  Make Yahoo! your home page now.
http://us.click.yahoo.com/DHchtC/3FxNAA/yQLSAA/9rHolB/TM
--------------------------------------------------------------------~-> 

Unsubscribe
[email protected]

List info
http://www.quirksmode.org/dom/list.html 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/wdf-dom/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/