The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

I'm on a roll now, just got XML::Filter::Cache written, which caches SAX
events to disk using Storable. It makes SAX parsing nice and fast (assuming
you've parsed once already).

Neat -- does it just Store each event's data to the disk file individually, so that parsing the file doesn't involve unStoring a whole structure of events? I can imagine efficiency gains either way (or inbetween), but I haven't gone benchmarking Storeable yet or anything.

It stores it all in one big file, but not in one big storable file - it's a simple record oriented file (i.e. 4 byte "length" marker followed by the Storable structure of that length). So it's all streaming. Of course that's just the default storage backend. I've hopefully made it flexible enough that you could do different storage backends.