because http is a complete mess that is impossible to get right.
my ISP likes randomly closing TCP sockets, and i am tired of hacking around insufficiently robust http implementations.
as far as i can tell, there is not a single extant http library that actually does things correctly out of the box. curl can get pretty close by throwing --continue-at - --retry-all-errors at everything, but even that doesn’t correctly handle mid-air collisions (you need If-Range for that, and I don’t know if there’s any easy way to do that with curl).
Seems meh. Why?
score 1 · canonical
because http is a complete mess that is impossible to get right.
my ISP likes randomly closing TCP sockets, and i am tired of hacking around insufficiently robust http implementations.
as far as i can tell, there is not a single extant http library that actually does things correctly out of the box. curl can get pretty close by throwing
--continue-at - --retry-all-errorsat everything, but even that doesn’t correctly handle mid-air collisions (you needIf-Rangefor that, and I don’t know if there’s any easy way to do that with curl).score 3 · canonical
And how does a new protocol that no one uses and will never use help with that?
score 2 · canonical
The point is to explore alternate design spaces.
score 2 · canonical