Why XML for data serialization? Do you need human readable cache storage? If not you could use
Storable instead of
XML::Simple.
- It is probably faster (I have not made any benchmarks though).
- It can handle binary data.
- It have no problems with preserving order.
Morever you could use Cache::Cache to handle caching. This module provides quite high level API for data cache (and AFAIK it uses Storable to serialize/deserialize data).
I've rewrote you example using Cache::Cache:
# init cache object at the begining of the program
my $CACHE = new Cache::FileCache( );
.....
.....
#### Cut, subroutine from module
foreach my $tid (@completed){
$results{$tid} = $CACHE->get($tid);
unless(defined $results{$tid}) {
$results{$tid} = $self->Complex_Crap($tid);
# data will expire in cache in 10 minutes
$CACHE->set($tid => $results{$tid}, "10 minutes");
}
}
$self->Results(\%results);
return($self);
}
Update: Added example of Cache::Cache usage.
--
Ilya Martynov
(http://martynov.org/)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.