ucjonathan
ucjonathan
I haven't done anything further with it.
I haven't spent any time looking at how the fetch API can be captured, but this Stackoverflow article seems to offer some ideas. https://stackoverflow.com/questions/45425169/intercept-fetch-api-requests-and-responses-in-javascript
I’m in favor of working with our own home grown code to minimize the runtime size as that is very important. We have the XHR figured out. Maybe later this...
The argument in favor of multiple blocking classes is... you can add the rr-block to elements that match your classes before starting the recording process, but you can't handle dynamically...
+1 for support for pipelining on a cluster. Would like to continue using Jedis libraries to talk to Elasticache without having to rewrite a bunch of existing code since pipelining...
I'd also like to see cluster pipelining as well. Tons of older code that we would have to re-write just to move to newer cluster deployment of redis. Can we...
I just bit the bullet and refactored the code to use JedisCluster and stop pipelining. It actually wasn't as bad as I had expected it to be.
Definitely can confirm this behavior. Thanks for taking the time to open this issue on GitHub. It was just the hint I needed to fix it.
@rubenschulz Thank you for posting that fix. Dealing with that exact issue right now!