Which still might be a valid option, even if as Roberto points out it's not the ideal area of the solution space. Similar to Upgrade, the first request(s) is/are made using vanilla HTTP plus any non-breaking extensions. After one RTT, you know which breaking extensions are safe to use. Sent from Windows Mail From: Eliot Lear<mailto:lear@cisco.com> Sent: ?Wednesday?, ?October? ?2?, ?2013 ?11?:?02? ?AM To: Eliot Lear<mailto:lear@cisco.com> Cc: Mike Bishop<mailto:Michael.Bishop@microsoft.com>, Amos Jeffries<mailto:squid3@treenet.co.nz>, Roberto Peon<mailto:grmocg@gmail.com>, James M Snell<mailto:jasnell@gmail.com>, ietf-http-wg@w3.org<mailto:ietf-http-wg@w3.org> On 10/2/13 7:33 PM, Eliot Lear wrote: Why not just define an optional capabilities exchange mechanism on Channel 0? Having seen Roberto's design constraint, nevermind.
Received on Wednesday, 2 October 2013 20:33:43 UTC