On Mon, Nov 26, 2007 at 07:24:34PM +0000, place wrote:

...

Yes. Send me this.

All right. Attached.

Committed.

...

...

2) Chunked Transfer-Encoding running on top of (1) because I thought it might help with gzip latency. It was a can-I-get-this-working-in-principle effort and I will have to rewrite it now. Plus I need to actually read through the http/1.1 spec (what I did was just based on a little web page that summarized the main differences between 1.0 and 1.1 for me).

Hmm, yes. Please rewrite it as simple/clean as possible, and with the SPEC in one hand. Once there, please send it.

My experience is that code written to comply with the SPEC is easier to debug and polish (there're plenty of cases where wrong behaviour is on the server side, and thus we can be sure is not dillo).

It sounds like somebody's indeed had his share of bitter experience with being sent hacked-together patches :) I wasn't actually threatening to send this version; just letting you know what's going on...

Yes, you're right. 8-P

The most annoying part so far was that 1.1 is supposedly able to send "100 Continue" before you get the real stuff. I haven't seen one actually do it yet, though. Maybe that's only if you're doing pipelining...

Oh, and I just read about multiline headers. It wasn't really clear whether this was new in 1.1, though. Did 1.0 have to handle it as well?

Multiline headers?! sorry, I don't remember that off the top of my head. -- Cheers Jorge.-