Comment #3 on issue 8991 by jmyers4: Optional HTTP pipelining mode http://code.google.com/p/chromium/issues/detail?id=8991
I have created three components for my own server that would be useful for the HTTP/1.1 pipelining effort. * Fast input recognition system: http://www.myersdaily.org/joseph/unix/listswitch.html http://soar.wichita.edu:8080/dspace/handle/10057/848 * Fast HTTP header processing: http://www.myersdaily.org/joseph/unix/server/ http://www.myersdaily.org/joseph/unix/server/readheader/index.html * Fast HTTP request parser: Based on the experiences gained from writing the easy.pm pragma and Web::* Perl modules, used world wide with no bugs found since July, 2000. Canonicalizes all operating systems by recognizing line ends with LF and ignoring CR. "The best decision Unix made was to use a single newline character." (Perl Cookbook) * Minimizes data copy operations by using independent structures for meta-data and IO streams. I would be interested in working on HTTP/1.1 support provided that I have graduated with my Ph.D. in applied math by then. If I still have research left I won't be able to do that. I plan to keep you posted. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
