Reading a little about HTTP 2.0 and SPDY, which seems destined to be a part
of HTTP 2.0 
  
 [ http://www.chromium.org/spdy/spdy-whitepaper ] 
  
 I'm not sure I want to implement this.  We haven't even implemented all of
the features of HTTP 1.1 in their entirety. 
  
 It would seem that a more sensible implementation might be to do the following:

  
 1. Regardless of operating mode, *always* use the "/webcit" (or perhaps "/wc")
prefix for every transaction 
    (exceptions would be things like "/dav" of course) 
  
 2. Increase the number of protocol modes to three: HTTP, HTTPS, and FastCGI.
 This would give administrators a choice of running WebCit as a standalone
web server (using HTTP 1.1 forever), or plugging it into any FastCGI-enabled
web server. 
  
  
  I know already that dothebart will be super happy about this idea.  :) 
 what do y'all think? 
 

Reply via email to