Jon Gjengset

Ah, fair enough. If `Range` is standardized to only be meaningful to GET and `Offset` is on the track for becoming a standard then I'd say go ahead with `Offset`...

How about `Entity-Available` over `Entity-Received`?

In my opinion, `Offset` doesn't make sense as a response to a HEAD/GET as the value describes the amount of content available, not an offset into that content.

@vayam in a way the timeout you show above has the same end result as having `Content-Length` == `Offset` - you only download as much of the file as available...

Wouldn't it then make more sense as we decided above to include `Entity-Available` in the response - that way conforming clients could decide what behavior they want based on whether...

Oooh, very excited for this! The one point I think warrants some discussion is the MSRV policy, which I know is a topic many people have opinions on. As we've...

I think it's pretty unlikely that a concurrent hash map will be completed and agreed upon for a 1.0. Not to mention that _adding_ something like that can be done...

`ArcCell` was removed in #301, so I assume this should be closed?

So, concache is pretty much just a linked hash table where the buckets use a [lock-free linked list](https://www.microsoft.com/en-us/research/wp-content/uploads/2001/10/2001-disc.pdf). It also doesn't currently support resizing, as that would (in the current...

I feel like we might be able to leverage `async`/`await` to deal with the progress tracking/continuation state rather than make the deserializer support re-entry. That would also allow arbitrary `Deserialize`...