Hi Rich, If you set up your object dependencies correctly then the objects you want will stay in memory. Your history list would be a list of WeakReference so it could be GC'd.
This is nothing about read tracking, more about setting the correct object dependencies so that the GC doesn't remove objects you aren't quite finished with yet. I been writing up a description here. It's a simplified version of what I've been playing with. http://creativereality.com.au/notes/concurrency/54-mvcc-stm-gcd-ref-history?start=1 I kept the Transaction objects on the list, but you could consider keeping a smaller object with just has a collection in it; associated with the transaction. -Peter -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
