seanmonstar / seanmonstar/httparse
Improve API
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 713
- Forks
- 135
- PR merge metrics
- No merged PRs in 30d
Description
I would like to build a function
fn read_headers<'a,'b,R: BufRead>(
stream: &mut R,
buf: &'b mut Vec<u8>,
headers: &'a mut [Header<'b>]
) -> Result<Request<'a,'b>,E>
that reads as much from stream into buf as necessary to get a Complete return from Request::parse. This turns out to not be trivial and require lots of extra allocations and work.
Here's what I came up with:
fn read_headers<'a,'b,R: BufRead>(clnt: &mut R, buf: &'b mut Vec<u8>, headers: &'a mut [Header<'b>]) -> Result<Request<'a,'b>,String> {
fn extend_and_parse<R: BufRead>(clnt: &mut R, headers: &mut [Header]) -> Result<Vec<u8>,String> {
let mut buf=Vec::<u8>::new();
let len=headers.len();
loop {
let buf_orig_len=buf.len();
let additional_len={
let additional=try!(clnt.fill_buf().map_err(|e|e.to_string()));
buf.extend_from_slice(additional);
additional.len()
};
let mut headers=Vec::with_capacity(len);
headers.resize(len,httparse::EMPTY_HEADER);
let mut req=Request::new(&mut headers);
match req.parse(&buf) {
Ok(httparse::Status::Complete(n)) => {
clnt.consume(n-buf_orig_len);
break
},
Ok(httparse::Status::Partial) => {
clnt.consume(additional_len);
}
Err(e) => return Err(format!("HTTP parse error {:?}",e)),
};
}
Ok(buf)
}
let result=extend_and_parse(clnt,headers);
result.map(move|nb|{
::core::mem::replace(buf,nb);
let mut req=Request::new(headers);
req.parse(buf);
req
})
}
The main issues are having to allocate a new array of temporary headers for every iteration, and having to parse the succesful result twice.
I think this is partially Rust's fault, but also partially httparse for having a not so great API. For example, the lifetime of everything is fixed upon Request creation, so that a parse failure doesn't release the borrow of the input buffer.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading Request::parse and the proposed read_headers function in the issue. Compare the parsing and buffer-lifetime behavior described there, then define an API approach that avoids repeated temporary header allocation and reparsing while preserving the requested result and stream consumption.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100