On Tue, Sep 07, 2010 at 09:43:50PM +0100, Mark Morgan wrote: > On 7 September 2010 20:52, Tim Bunce <tim.bu...@pobox.com> wrote: > > > > Assuming you go with this approach (did I mention it was highly > > recommended :) then your logic would live in a Gofer transport class > > like DBI::Gofer::Transport::TotalCache. > > > > You'd select it using something like: > > > > DBI_AUTOPROXY="dbi:Gofer:transport=TotalCache;file=foo;mode=record" > > Cheers for that, Tim. I had a brief look at Gofer earlier last week, but > abandoned it when realized it had no transaction support (one of the > requirements for my current need).
How do you see transaction support interacting with the underlying recording and playback behaviour? > I'll have a look at this again. It does > seem custom-made for this type of problem. It was the Gofer slideshare that > actually inspired this idea; I (rightfully) disgusted one of my current > colleagues with the idea of using DBD::Gofer with HTTP transport and > wrapping that with LWP::UA::Mockable. ;) Yeah! That's the kind of crazy plumbing idea I like ;-) Tim.
