nilern/eximia

A fast and small XML processor for Clojure. With XML namespace support and secure defaults.

eximia's Issues

Add support for babashka

It would be great if this library would work with https://github.com/babashka, maybe as a pod.

Is there a way to consume XML elements lazily?

I've been using Eximia and have been very pleased with its performance and simplicity.

However, I'd like to use Eximia to operate on large documents in a memory-constrained environment (AWS Lambda)

The parsing seems to eagerly process all of the XML input which consumes a lot of memory and places a hard limit on the size of input that can be processed. For example, if I load a 29MiB input document, my Lambda reports a memory usage of 780MiB.

Would it be possible to have an option to consume the stream of XML tokens lazily, say via a lazy seq?

Lazy default factory creation

Your comments suggest that factory creation is expensive:

Note that XMLInputFactory instances can be very expensive to create but are reusable. So call this as rarely as
possible, probably only in the application startup phase.

I'm using Woodstox with Eximia and it looks like the default input factory is created eagerly and is unnecessary in my case:

(def ^:private ^XMLInputFactory default-input-factory (input-factory {:coalescing true}))

I'm using Eximia in AWS Lambda, natively compiled with GraalVM**. The XML libraries can touch a lot of classes under the hood. This will cause GraalVM to pull those classes into the native build, so anything that can be done to avoid touching/instantiating unnecessary code will yield tangible improvements in deployment size and startup time (especially from cold starts).

** see https://github.com/FieryCod/holy-lambda