Hi Ludger, Oddly enough I was thinking about this (again) yesterday while I was fixing some bugs in the Range implementation.
Definitely interested in moving to WeakReferences. NodeIterators, EventListeners, user data and probably a few other things in the DOM implementation which hold on to objects which could otherwise be garbage collected would also benefit from this. It's been on my TODO list since we dropped JDK 1.1 support, though I first wanted to check what impact it would have on performance and serialization compatibility (i.e. java.io.Serializable) if any before committing these improvements. Just haven't gotten around to it yet. Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] "Ludger Buenger" <[EMAIL PROTECTED]> wrote on 03/07/2007 11:12:54 AM: > Hello Mr. Glavassevich, > > Since I am not actively registered to the xerces-mailinglist and > unsure whether this is an issue with regards to the xerces > philosophy, I write to you as the one most involved with this project. > > During development we discovered that DOM ranges always have to be > detached as defined by the DOM Range specification. > > This sure is a useful behaviour for a general API but since Java has > an inbuild-garbage-collector there is no need to have to rely upon > external developers allways actively detaching a range (however it > still might be desirable). > > Since I patched xerces for our own product to use garbage- > collectable ranges, I'd like to ask whether you or the community is > interested to add this 'feature'? > > Sincerely yours, > > Ludger Bünger > > -- > Ludger Bünger > RealObjects GmbH --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
