incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "TrafficServerProposal" by LeifHedstrom
Date Thu, 11 Jun 2009 05:28:17 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The following page has been changed by LeifHedstrom:
http://wiki.apache.org/incubator/TrafficServerProposal

------------------------------------------------------------------------------
  The goal is to create an Apache top level project around the existing Traffic Server project.
Traffic Server (TS for short) is an existing piece of software developed by Yahoo!, which
is used to deliver significant amount of HTTP traffic to millions of users.
  
  Key Features:
-  * Full HTTP/1.1 proxy server
+  * HTTP/1.1 caching proxy server
   * Scalable on SMP (TS is a hybrid thread + event processor)
   * Extensible; TS has a feature rich plugin API
   * Fast.
@@ -19, +19 @@

  Traffic Server is a piece of software initially acquired by Yahoo! from Inktomi. The software
has been actively developed and used at Yahoo for the last three years, and we're now getting
ready to Open Source this project.
  
  == Rationale ==
- Traffic Server fills a need to provide fast, extensible and scalable HTTP proxy and caching.
We provide a proven piece of software, that can deliver HTTP content at high rates, and that
can scale well on modern SMP hardware. Traffic Server has a rich feature set, implementing
most of HTTP/1.1 to the RFC specifications.
+ Traffic Server fills a need to provide a fast, extensible and scalable HTTP proxy and caching.
We have a production proven piece of software, that can deliver HTTP traffic at high rates,
and can scale well on modern SMP hardware. We ave benchmarked Traffic Server to handle in
excess of 35,000 QPS on a single box. Traffic Server has a rich feature set, implementing
most of HTTP/1.1 to the RFC specifications.
  
  == Initial goals ==
- The the initial goal is to build a community of developers, and users, of the Traffic Server
software.
+ The the initial goal is to build a community of developers, and users, of the Traffic Server
software. Longer term goal is to address a few feature additions that we think are highly
beneficial:
+ 
+  * Full 64-bit support
+  * Porting to more Unix flavors
  
  == Current Status ==
  
  === Meritocracy ===
- Meritocracy is one of the fundamental reasons why we want to Open Source Traffic Server
to begin with. Building an active developer community is a critical goal, attracting active
and skilled developers that are willing to contribute is vital
+ Meritocracy is one of the fundamental reasons why we want to Open Source Traffic Server
to begin with. Building an active developer community is a critical goal, attracting active
and skilled developers that are willing to contribute is vital to our success.
  
  === Community ===
- Our hope is that our existing code, features and capabilities will attract a large community
of both developers and users. We know that several developers who have previously worked on
the code are looking forward to participate in the Open Source efforts.
+ Our hope is that our existing code, features and capabilities will attract a large community
of both developers and users. We know of several developers who have previously worked on
the code are looking forward to participate in the Open Source efforts. The user community
of Traffic Server would be similar to that of the Apache HTTP server, and in man cases they
would overlap.
  
  === Core Developers ===
   * Leif Hedstrom <leif at yahoo-inc.com>
@@ -40, +43 @@

   * Dima Ruban <dima at yahoo-inc.com>
  
  === Alignment ===
- Yahoo! is already a contributor to the Apache Foundation, and it's easier and safer for
us to stick to one Open Source partner. We are already familiar with the ASF process, and
we know it provides everything we need and require to be successful.
+ Yahoo! is already a contributor to the Apache Foundation, and it's easier and safer for
us to stick to one Open Source partner. We are already familiar with the ASF process, and
we know it provides everything we need and require to be successful. We also feel there is
a natural symbiotic relationship between Traffic Server and the Apache HTTP server, which
is how TS is generally used at Yahoo.
  
  == Known Risks ==
  
@@ -48, +51 @@

  Traffic Server is widely used and deployed inside of Yahoo. It's not going away anytime
soon, in fact, it's growing fast
  
  === Inexperience with Open Source ===
- Most participants are active users and contributors to open source. Leif is a committer
at Mozilla (although, no longer active).
+ Most Yahoo participants are active users and contributors to open source projects. Leif
is a committer at Mozilla (although, no longer active), as well as maintainer of a Yahoo search
API (pYsearch).
  
  === Homogeneous Developers ===
- The current list of committers are members of the Yahoo developer team only. The hope is
that we can quickly attract new members, either people just interested in the technology,
or people familiar with the code base from previous employments.
+ The current list of committers are all members of the Yahoo developer team. The hope is
that we can quickly attract more members, either people just interested in the technology,
or people familiar with the code base from previous employments.
  
  === Reliance on Salaried Developers ===
  All initial committers are salaried employees of Y!.
@@ -69, +72 @@

  All code is currently in-house at Yahoo, and we're working on getting it cleaned up and
cleared to be uploaded to the Apache SVN servers.
  
  == Source and Intellectual Property Submission Plan ==
- All TS code is fully owned by Yahoo! Inc, and we're finalizing all the legal paperwork around
releasing it as Open Source, under the Apache license. We've hired an external entity to do
full code review of all source files, to assure it's not tainted.
+ All TS code is fully owned by Yahoo! Inc, and we're finalizing all the legal paperwork around
releasing it as Open Source, under the Apache license. We've hired an external company to
do full code review of all source files, to assure it's not tainted. The cleaned code of Yahoo
Traffic Server would become the Apache Traffic Server.
  
  == External Dependencies ==
  Traffic Server have no external dependencies, other than standard libraries like BDB, OpenSSL,
TCL, STL, glibc and expat.

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message