Bert, I do not understand. How do you want to make pipelining requests and protocol upgrades work together? I assume you talk about http pipelining where you send a second request before you receive the response for the first one...
//Stefan > Am 08.12.2015 um 11:27 schrieb Bert Huijben <b...@qqmail.nl>: > > > >> -----Original Message----- >> From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] >> Sent: dinsdag 8 december 2015 10:43 >> To: dev@httpd.apache.org >> Subject: Re: 2.4 pause - mod_http2 patchset Upgrade h2c vs mod_ssl >> Upgradetls > > >> If Apache accepts body lengths of up to 64KB (or something configurable) >> and some other server implements 8K and some third 1MB, how will that >> help design of a client that, for some reason, *wants* an upgrade to >> succeed? > > For Subversion this would make a 100% difference. > > Currently all true Subversion servers are implemented via httpd. > > > Upgrade to h2c is currently not interesting for webbrowsers as all of them > have decided not to implement it... But it makes a huge difference for web > applications that talk to specific servers. > > Which is very similar to that TLS upgrade that is interested for > webprinting... These usecases don't use combinations of random clients, with > random servers... They use specific combinations. > > Bert >
