Right now the cookie caching code assumes the cookie storage is on a local disk. This works fine if you run all your rets interactions on a single machine or have some sort of shared filesystem, but it's not terribly flexible.
I'd prefer a caching mechanism that accepts an object that responds to read(name) and write(name) or something similar, then we can write plugins for this for nearly any storage system and simplify the process of running rets clients on multiple machines.