- From: Helge Hess <helge.hess@opengroupware.org>
- Date: Sun, 17 Feb 2013 17:38:13 -0800
- To: William Chan (陈智昌) <willchan@chromium.org>
- Cc: James M Snell <jasnell@gmail.com>, Roberto Peon <grmocg@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>, Phillip Hallam-Baker <hallam@gmail.com>, Cyrus Daboo <cyrus@daboo.name>
On Feb 17, 2013, at 5:30 PM, William Chan (陈智昌) <willchan@chromium.org> wrote: > I'm having difficulty grokking this proposal. Can you describe more clearly how this would work with the web platform? Specifically, what kind of markup in a HTML document should cause a browser to use a MGET for a resource set as you describe it. ? e.g. <img>, <script>, CSS links etc. > Also, how does this work for HTTP/1.X? Since we'll be living in a transitional world for awhile, I'd like to understand how this allows for HTTP/1.X semantics backwards compatibility. An old server would return a 405 when the BATCH comes in, then the client needs to switch to performing the operations individually. hh
Received on Monday, 18 February 2013 01:38:38 UTC