4 ms·
Long story short, we forked the major browsers so that when you record we can capture the browser input (OS Library calls). Brian walks through our approach he
by jasonlaster11 5y ago
Long story short, we forked the major browsers so that when you record we can capture the browser input (OS Library calls).
Brian walks through our approach here https://medium.com/replay-io/how-replay-works-5c9c29580c58 https://medium.com/replay-io/how-replay-works-5c9c29580c58
- maxmcd 5y agothank you!
- donio 5y agoHow will this work on the long run? Will you try to upstream the required changes or will the forks have to be maintained perpetually?
- jazzdan 5y ago(Replay engineer): In the long run we'd love for Replay to prove to the major runtimes that they should build support for this in to the runtime itself, rather than us maintaining many forks. The API that we designed for recording a runtime is open source and available here https://replay.io/driver https://replay.io/driver and could serve as a good starting point.
- eurasiantiger 5y agoThat’s gonna be a pipe dream unless an open source client appears. Consider releasing your tech as a self-hosted, turnkey solution and slap on some dual enterprise licensing.
- jazzdan 5y agoSelf-hosted is on the roadmap, but getting this to be a universal technique is definitely going to be hard, no arguments there. Gotta start somewhere though!