We have to take into account that this mode of operation does not allow concurrent execution of tests against the same mock URL (unless your responses are setup to `FOREVER` and you never check history). So maybe we could add a note about this.

Maybe a better future approach could include filtering datasets by originating IP or something like that.
The mock client could be set up with some parameter saying: this mock is for requests coming from this server...