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

What's the plan? #12

Closed
meteor-lsw opened this issue Jun 4, 2019 · 3 comments
Closed

What's the plan? #12

meteor-lsw opened this issue Jun 4, 2019 · 3 comments

Comments

@meteor-lsw
Copy link
Contributor

As we can see, your last commit was almost 3 years ago. So, what's the plan?

Are you still working on this?

@meteor-lsw
Copy link
Contributor Author

In these 3 years, both redis and rust have changed a lot.

@seppo0010
Copy link
Owner

seppo0010 commented Jun 4, 2019

I am not working on this. I have no plan to move forward with it.

@seppo0010
Copy link
Owner

If you want to make something like this, I would suggest to start from scratch. There are many unaddressed issues that require consideration from the beginning (for example, how to handle parallelization if wanted), many things that can be done in a more rust-y way (using nom, failure, serde, env_logger) and other things that can be done more efficiently (for example not returning a Response object but instead receiving a write-like object to write the response, avoiding unnecessary memory copy).

I think it was a fun learning experiment for me, but I don't think it is useful in any way.

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