You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 23, 2018. It is now read-only.
I would like to offer you help in creation of this middle-ware http library for Rust. I'm very new in Rust world, but this language captured my mind and I want practice with it to expand language infrastructure.
I'm also thought to create http library for rust, but you was first. Your early http project was good start. And new teepee could be modern and high performance http library.
Currently I'm working on headers parsing algorithm here. Actually I'm only at start and work in secondary branch.
In my opinion, http library could be more granular. Not just an server side or client side. It could be collaboration of many simple Crates that independent to each other. For example - http headers parsing - could be very stand alone crate that can be used not only in teepee http protocol implementation. Or chunk reader, that also can be used in many other custom http stream readers.
My current goal is to create high performance http headers parser, that do not prepare all headers at start, but create efficient structure to work with headers. Maximum headers data should stored in raw vector and prepare for user on demand. I'm from .NET world and there is a very useful HttpHeaders class with two descendants for request and response headers. I want to create something similar but in Rust style.
Can we unite our projects and work together?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello.
I would like to offer you help in creation of this middle-ware http library for Rust. I'm very new in Rust world, but this language captured my mind and I want practice with it to expand language infrastructure.
I'm also thought to create http library for rust, but you was first. Your early http project was good start. And new teepee could be modern and high performance http library.
Currently I'm working on headers parsing algorithm here. Actually I'm only at start and work in secondary branch.
In my opinion, http library could be more granular. Not just an server side or client side. It could be collaboration of many simple Crates that independent to each other. For example - http headers parsing - could be very stand alone crate that can be used not only in teepee http protocol implementation. Or chunk reader, that also can be used in many other custom http stream readers.
My current goal is to create high performance http headers parser, that do not prepare all headers at start, but create efficient structure to work with headers. Maximum headers data should stored in raw vector and prepare for user on demand. I'm from .NET world and there is a very useful HttpHeaders class with two descendants for request and response headers. I want to create something similar but in Rust style.
Can we unite our projects and work together?
The text was updated successfully, but these errors were encountered: