Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Matts (1087)

Matts
  (email not shown publicly)

I work for MessageLabs [messagelabs.com] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.

Journal of Matts (1087)

Monday January 28, 2002
10:53 AM

On a roll...

[ #2468 ]

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).

Next onto the more tricky bits of AxKit - XSP and AxPoint. AxPoint first as its easier.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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.

    Also, is this for caching any bunch of SAX e

    • 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.

      It'll cache SAX events from anything.