8000 What's the first milestone for this project? · Issue #61 · haywire/haywire · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

What's the first milestone for this project? #61

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.

Sign up for GitHub

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

Jump to bottom
Open
tobz opened this issue Jul 14, 2015 · 4 comments
Open

What's the first milestone for this project? #61

tobz opened this issue Jul 14, 2015 · 4 comments
Labels
discussion

Comments

@tobz
Copy link
Contributor
tobz commented Jul 14, 2015

You posted on Twitter that you were curious if people would want to help work on Haywire -- and I think that was a resounding "yes" :). However, what I don't see is a roadmap of what's left to be done overall.. or sort of... what defines a good milestone?

Do you have any sort of idea what Haywire v1.0 should look like? Do you think it's worth coming up with some ideas of what it might look like?
@kellabyte
Copy link
Collaborator

This is what I have so far. I would like to discuss other features or things that need completion for a first stable release.

https://github.com/kellabyte/Haywire/milestones/Version%200.1

@kellabyte
Copy link
Collaborator

@tobz @nmdguerreiro Let's revisit this discussion. What kinds of things would we want in an initial release? What should it look like? Here are my thoughts.

  • File based logging.
  • Needs to perform under long running benchmarks.
  • Needs to not leak memory under long running benchmarks.
  • Needs to be more stable than it is currently.
  • Needs to sustain high connection counts reliably with good throughput.
  • Needs to handle HTTP 1.1 keep-alive behaviour correctly.
  • I would like to have pico http parser merged in mainline with the above stability and performance.
  • TLS?
  • Zero-copy would be nice but we could start the experiments now but polish it for a second milestone.
  • Make a better story for the /stats route.

Routing currently isn't all that useful. It does a couple things but not much. Is that good enough for an initial milestone? If not, what routing features do we need?

Any other thoughts?

@nmdguerreiro
Copy link
Contributor

In my use case, I'll definitely need some sort of file-based logging. Would it make sense to make it part of the first milestone?

@kellabyte
Copy link
Collaborator

@nmdguerreiro 👍 I think that's a good idea :) I'll update the list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tobz @kellabyte @nmdguerreiro
0