Hi Mark Renouf
Thank you for reply.
Let me try to give an example (maybe not very appropriate).
I create tree on page. I get data for that tree from server. I can get
data for all tree nodes to construct tree, or make new requests to
server when user opens new nodes. Suppose whole tree is too
Yeah, it's quite doubtful. The technique I would see JS engine writers
adopting would be an event generated indicating low memory (so the app can
remove cached memory). However, this would be a far off time in the
distance, if ever would take a while to trickle into browsers as a
standard
Garbage collection in JavaScript is browser-dependent, but similar
rules apply as with Java. When you are no longer using the data, make
sure you eliminate all references to it. For example, if you've stored
it in an Array or Collection of some sort, be sure to null out or
remove those entries.
I have GWT application. Use loads page, then visits links (I use GWT's
Hyperlink, so page is not reloaded). Amount of data that page contain
is increased (I use AJAX requests to get data from server). I have
some data that shouldn't necessarily exist always, I can load it from
server again. Is
