Re:Announcing the `http` crate
by JoshTriplett on Monday July 31, 2017 @08:28PM
(#14897018)
Agreed. And in particular, these kinds of types would make it much easier to write a framework-agnostic library that helps you handle caching correctly, built on top of these types, like Request and Response.
[ Parent
| on HN ]
I'd argue that at the API level, these things should be required to think about. Any level of "help" so that I don't have to worry about cache headers should be from a framework that tells me what they think about them.
Re:Announcing the `http` crate
by JoshTriplett on Monday July 31, 2017 @10:50PM
(#14897568)
> I'd argue that at the API level, these things should be required to think about. Any level of "help" so that I don't have to worry about cache headers should be from a framework that tells me what they think about them.
Agreed completely. The lowest-level API should expose them and every other bit of the standard, and higher-level APIs should handle them automatically in sensible ways.