XOM API for Processing XML with Java

[Peter Murray-Rust <pm286 AT cam.ac.uk>]

[comment] IRC the idea of the construct was raised on XML-DEV some time in
1997 as an oddity (not with the Billion Laughs text) and the general
reaction was - nobody would do that sort of thing, would they? Can't find
the exact post, will keep looking. And I think people thought that XML
didn't have serious security problems.  I'd be interested to know when it
became an accepted exploit.




On Sat, May 3, 2014 at 11:23 AM, Dave Pawson <dave.pawson AT gmail.com> wrote:

> On 3 May 2014 10:42, Elliotte Rusty Harold <elharo AT ibiblio.org> wrote:
>
> > Two more ideas:
> >
> > 1. Should the default limit be based somehow on available memory? and if
> so
> > what? e.g. XX% of the heap size?
> > 2. Is it plausible to simply catch an OutOfMemoryError in the Builder and
> > clean up, or would the system be hosed enough at that point, that cleanup
> > isn't reliable?
>
> I'll leave 2 up to you, I have no idea how degraded the system is
> when the out of memory error is raised.
>
> Pareto?  you raise the error at 80% of heap size, with clear error?
>
> HTH
>
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> Docbook FAQ.
> http://www.dpawson.co.uk
> _______________________________________________
> XOM-interest mailing list
> XOM-interest AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/xom-interest
>



-- 
Peter Murray-Rust
Reader in Molecular Informatics
Unilever Centre, Dep. Of Chemistry
University of Cambridge
CB2 1EW, UK
+44-1223-763069