Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comparison with goreplay #18

Open
tomkel opened this issue Apr 24, 2017 · 1 comment
Open

Comparison with goreplay #18

tomkel opened this issue Apr 24, 2017 · 1 comment

Comments

@tomkel
Copy link

tomkel commented Apr 24, 2017

I'm not understanding the high-level differences between this and goreplay. They seem to occupy most of the same problem space. Can someone explain if and how they differ in their use cases?

@sf1152
Copy link
Contributor

sf1152 commented May 23, 2017

I think the idea is the same. I didn't dig into goreplay but something I found out:

  1. goreplay implemented in go not sure if it can be used for other languages
  2. The example doesn't show how to support Http.
  3. It supports more protocol such as binary protocol.

For 3, we are going to support that soon. To share some idea how we want to support different protocol:

  1. Based on first a few bytes, we can decide if it's CONNECT or any other Http method or random bytes.
  2. If it's CONNECT, establish TCP connection
  3. If it's HTTP METHOD, decode using HttpDecoder
  4. If it not 2 or 3, then store whatever bytes somewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants