Does the job as documented. This is a good solution to implement cloning quickly. However be careful if you do a lot of cloning for I found this plugin to be 50x slower than an ad-hoc cloning implementation.
In short. If you don't clone too often, use this. If you do a lot of cloning, invest into writing your own ad-hoc one.
Template toolkit is the MySQL of Templating Systems. It does the job as long as you don't want too much sophistication.
It's good for non-developers to maintain simple things, like message templates for instance. And it's very easy to have it to fetch templates from different sources (like your DB).
Except that, the syntax and the behaviour is not consistent with what we're used to in Perl, making it a poor choice for us Perl developers. Unless you feel confortable with switching to a much less powerfull and much more confusing language when comes the time to write your View components.
If you're developing an Interface to a third party API using LWP, this is exactly the module you're looking for if you want to 'freeze' your test suite:
- Write tests as usual.
- Once happy, add this to them
- default to replay mode.
One caveat through: If your test rely on Time, you might experience some issues. To fix that, make sure you don't use changing time in your tests. Specificaly, replace 'now' by whatever fixed time it was when you froze the tests.
Great module. The api is almost exactly the same as the java one.
I tested it in a persistent environment ( mod_perl ) without any major problems. I use it with a couple of Gigs index containing millions of documents and it delivers astonishing performance.