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 given as far as I'm concerned. Whenever Teepee
materializes, we'll have to evaluate it on its own merits relative to
Servo's needs.
One option is to simply fork rust-http and replace most of the complicated
strongly-typed objects with simpler ones, and separate out the parsing
code. I probably can do this, but I'm not sure. This might even be useful
as a permanent replacement for rust-http (that we maintain) since it's
simpler and we don't really use the bits I propose to replace except in XHR
(which would be simplified by the change).
Couple of questions:
- Do we want a Fetch crate? If so, what's the best way to handle its
http library? (One option is to simply wait for Teepee)
I personally think it's likely a worthwhile endeavor to start on an HTTP
client crate. As I understand things, browsers haven't had a lot of luck
reusing external HTTP libraries, because their needs are so specific
(perf and bug-for-bug compatibility with every weird Web server out there).
There's also the issue of SSL support. We need it sooner rather than
later, because we're starting to want to really do testing against
top-100 sites and a large number of them are SSL-only.
This is not meant as a slight against Teepee; if we need to, we can
merge our work or switch over, as the case may be.
Patrick
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
