[dev-servo] rust-http, Teepee, and Fetch

*I was going to bring this up in today's meeting, but I'm not sure if I can turn up due to Internet issues.* So I've been working on CORS on the past week, and it's more and more evident that it would be best if most of the Fetch spec (except the webidls at the bott

Re: [dev-servo] rust-http, Teepee, and Fetch

On 7/7/14 6:17 AM, Manish Goregaokar wrote: Teepee is the replacement for rust-http but it's progressing rather slowly right now. It's also "over-engineered" (as Simon puts it), but it seems to fix most of rust-http's problems. I guess we'll eventually be switching over to Teepee. That's not a

Re: [dev-servo] rust-http, Teepee, and Fetch

I don't know that thinking about a fetch crate in terms of a submodule is particularly useful. I guess the idea is that it would be easy for other Rust programmers who want to make HTTP requests, but that sounds like a better fit for an API that is part of an HTTP crate, rather than trying to a

Re: [dev-servo] rust-http, Teepee, and Fetch

Okay, so the past few days I've been playing around with rust-http. The main issue is that the headers code stores pre-parsed headers (as strings or other types), doesn't handle badly encoded headers too well, and makes mistakes while encoding (leading to icky workarounds like this

Re: [dev-servo] rust-http, Teepee, and Fetch

Sorry, the link is https://github.com/Manishearth/rust-http/compare/chris-morgan:master...Manishearth:discombobulate -Manish Goregaokar On Sat, Jul 19, 2014 at 1:40 AM, Manish Goregaokar wrote: > Okay, so the past few days I've been playing around with rust-http. The > main issue is that the h

Re: [dev-servo] rust-http, Teepee, and Fetch

On 7/18/14, 4:10 PM, Manish Goregaokar wrote: - Rewrite the Header class to contain bytes Note that you need header bytes for web APIs like XMLHttpRequest. -Boris ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/li