Issue entered final state: How often (and what) is being ...

From: ETA WCA issues tracking forum (www-wca@w3.org)
Date: Sun, Jun 27 1999


Date: Sun, 27 Jun 1999 19:19:41 -0400 (EDT)
Message-Id: <199906272319.TAA07223@www19.w3.org>
To: WCA default <www-wca@w3.org>
From: ETA WCA issues tracking forum <www-wca@w3.org>
Subject: Issue entered final state: How often (and what) is being ...


This is an automatic ETA Notification:
   Your role as contact: You have been notified as a potential owner    
   Type of notification: Issue entered final state                      

Issue Summary:
             Forum: WCA issues tracking forum [1]                       
             Issue: How often (and what) is being tunneled through HTTP? [2]
          Category: HTTP                                                
          Priority: important                                           
             State: resolved                                            

        Created on: 1999-06-27 19:16:47                                 
        Created by: Henrik Frystyk Nielsen [3]                          
       Assigned to: WCA default [4]                                     

Issue Description:
--------------------------------------------------------
Rather than incurring the extra packaging overhead in tunneling, it
would be nice to make HTTP-NG semantically (and mechanically) rich
enough so that tunneling was not required. Mike Spreitzer added what
should/will be converted to the lower RPC layer with what should/will
remain at the higher RPC layer? How much CGI activity is going on?
CGI typically causes an expensive process creation, with parameter
passing (clumsily) through standard IO. Designing HTTP-NG to avoid the
inherent overhead in this approach and to provide a well
structured/defined, argument and return value framework would be
beneficial.
--------------------------------------------------------

Issue Resolution:
--------------------------------------------------------
HC97 server analysis shows that only 1% of the requests to a variety
of servers were for CGI material. These requests accounted for less
than 1% of the total bytes transferred. The most common uses of CGI
applications were (in order of occurrence): page counting and
redirects. HC97 also noted that the percentages of CGI traffic did not
increase during the course of their measurements. However, for one of
the sites in the HC97 study, 34% of the requests were for CGI material
accounting for 62% of the bytes transferred. While the majority of
requests and traffic are not CGI related, further consideration of
those sites that are composed primarily of CGI requests seems
necessary.
  
From the entire set of AOL97 traces, 1.15% of all requests were POST
requests. From a brief manual inspection of the requests, the most
common uses of POST are (not in order of occurrence): searching of
content, accessing databases, playing games, quoting stocks, and
custom applications. For the AOL97 traces, 9.64% of all GET requests
appended material. For GET requests that append data onto the end of
the URL, the most common applications are (not in order of
occurrence): page counting, redirects, content search, electronic
commerce, Web-based email, image maps, and Web page posting.

It is also important to note that "Characterizing World Wide Web
Queries" by Ghaleb Abdulla, Binzhang Liu, Rani Saad and Edward A. Fox
provides a characterization of WWW queries.
--------------------------------------------------------

References:
[1] http://cgi.w3.org/ETA/forums.php3/wca/?forums_id=2
[2] http://cgi.w3.org/ETA/issues.php3/wca/?issues_id=140
[3] http://cgi.w3.org/ETA/contacts.php3/wca/?contacts_id=2
[4] http://cgi.w3.org/ETA/contacts.php3/wca/?contacts_id=1