- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 28 Apr 2014 13:31:16 +0200
- To: Mark Nottingham <mnot@mnot.net>
- CC: Matthew Kerwin <matthew@kerwin.net.au>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
On 2014-04-28 13:23, Mark Nottingham wrote: > > 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... It's an issue for server->client, but not the other way around... (unless I'm missing something?) Best regards, Julian
Received on Monday, 28 April 2014 11:31:52 UTC