Why
Users should be able to record all traffic for under a specific session key, then pick a session recording at a later point.
What
- Build a server api to handle
session recording (start/stop) and playback (start/stop)
- Build in UI support to call these APIs
Difference in behavior for a session vs basic jambox functionality:
- A
session should only record requests when prompted, no recording of requests during playback of any kind
- A
session should record all requests as unique entities, recorded chronologically. Should perform no hashing/de-duplication. It's possible this may be configurable in the future.
Consider calling session a tape to match the theme of a jambox being another name for a boombox.
Why
Users should be able to record all traffic for under a specific
sessionkey, then pick asessionrecording at a later point.What
sessionrecording (start/stop) and playback (start/stop)Difference in behavior for a
sessionvs basic jambox functionality:sessionshould only record requests when prompted, no recording of requests during playback of any kindsessionshould record all requests as unique entities, recorded chronologically. Should perform no hashing/de-duplication. It's possible this may be configurable in the future.Consider calling
sessionatapeto match the theme of a jambox being another name for a boombox.