- From: Mark Nottingham <mnot@mnot.net>
- Date: Mon, 28 Apr 2014 21:23:27 +1000
- To: "Julian F. Reschke" <julian.reschke@gmx.de>
- Cc: Matthew Kerwin <matthew@kerwin.net.au>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
On 28 Apr 2014, at 9:22 pm, Julian Reschke <julian.reschke@gmx.de> wrote: > On 2014-04-28 12:45, Matthew Kerwin wrote: >> ... >> How does your non-browser client discover that the resource exists in >> the first place, or can be POSTed or PUT to? That's the place to add > > HEAD? PROPFIND? AtomPub? > >> that it can handle zipped files. Whether that be in the linking >> hypermedia, or offline API documentation, or a new link extension in a >> Link header, etc. >> ... > > Yes, many ways to do that. But there should be a single way, so that middleware can do it automatically. As discussed, “middleware can do it automatically” and content-encoding don’t mix so well... -- Mark Nottingham http://www.mnot.net/
Received on Monday, 28 April 2014 11:23:53 UTC