Gábor Csárdi

Is this all what we needed, @jennybc ?

@richfitz Thanks! Let us try the namespacing and we'll see if it indeed solves our problem.

> Since I assume httrmock will keep using RDS, then this will mean lots of directories? Yes. > If I follow, we could end up using a new httrmock context...

Well, to be fair there is `httrmock::list_recordings()`..... but yes, we'll use namespaces....

> it will change pretty much every run there is a write. That's the thing, this is not ideal, you don't have a clue what is changing.

Namespaces are an improvement, but still not the real thing: https://github.com/gaborcsardi/httrmock/issues/4#issuecomment-266875686

I thought about a git backend as well, but a generic git backend for storr would look probably quite different than what we need here. A generic backend would probably...

@richfitz Thanks! This is a big step towards our use case, but it is still not there unfortunately, because we often a different key and filename. This is simply because...

OK, sorry, I don't expect you to squeeze our use case in storr. :) I might create a PR, if it seems fitting, though.

I don't mind, I am fine wil PRs as well for now. :)