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 22:43:55 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

------------------------------------------------------------------------------
  Traffic Server is fast, scalable and extensible HTTP/1.1 compliant caching proxy server.
  
  == Proposal ==
- 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.
+ The goal is to create an Apache top level project around the existing Yahoo! Traffic Server
project. Traffic Server (TS for short) is an existing piece of Yahoo! software, which is used
in-house to deliver significant amount of HTTP traffic to millions of users.
  
  Key Features:
   * HTTP/1.1 caching proxy server
   * Scalable on SMP (TS is a hybrid thread + event processor)
-  * Extensible; TS has a feature rich plugin API
+  * Extensible: TS has a feature rich plugin API
-  * Fast.
+  * Fast
  
  == Background ==
  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 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 have benchmarked Traffic Server to handle in
excess of 35,000 RPS on a single box. Traffic Server has a rich feature set, implementing
most of HTTP/1.1 to the RFC specifications.
+ Traffic Server fills a need for 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 have benchmarked Traffic Server to handle in
excess of 35,000 RPS 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. Longer term goal is to address a few feature additions that we think are highly
beneficial:
+ 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
+  * Porting to more Unix flavors (currently we only support Linux)
  
  == Current Status ==
  
@@ -33, +33 @@

  Building our developer community using the meritocracy is important to the success of Traffic
Server. We know there are many developers out there interested in the technology, and the
meritocracy system is a great way to encourage participation.
  
  === Community ===
- 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. We also believe that
other organizations will find this project interesting and relevant, and contribute resources.
+ 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 participating in the Open Source efforts. We also believe
that other organizations will find this project interesting and relevant, and contribute resources.
  
- The user community of Traffic Server would be similar to that of the Apache HTTP server,
and in man cases they would overlap.
+ The user community of Traffic Server would be similar to that of the Apache HTTP server,
and in many cases they would overlap.
  
  === Core Developers ===
   * Leif Hedstrom <leif at yahoo-inc.com>
@@ -45, +45 @@

   * 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. 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.
+ Yahoo! is already a contributor to the Apache Foundation. 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 ==
  
  === Orphaned Products ===
- Traffic Server is widely used and deployed inside of Yahoo. It's not going away anytime
soon, in fact, it's growing fast
+ 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 Yahoo participants are active users and contributors to open source projects. Leif
is a committer at Mozilla (although, no longer active), creator of PerLDAP, as well as maintainer
of a Yahoo search API (pYsearch).
+ Most Yahoo! participants are active users and contributors to Open Source projects. Leif
is a committer at Mozilla (although no longer active), creator of PerLDAP, as well as maintainer
of a Yahoo! search API (pYsearch).
  
  === Homogeneous Developers ===
- 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.
+ 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 employment.
  
  === Reliance on Salaried Developers ===
- All initial committers are salaried employees of Y!.
+ All initial committers are salaried employees of Yahoo!.
  
  === Relationships with Other Apache Products ===
  Traffic Server integrates well with the Apache HTTP daemon, as a proxy and cache.
  
  === An excessive fascination with the Apache brand ===
- Our decision to apply to the ASF is simple - Y! has already contributed several projects
to the ASF, and the Apache collaboration model and license further Y!'s goals.
+ Our decision to apply to the ASF is simple. Y! has already contributed several projects
to the ASF, and the Apache collaboration model and license further Yahoo!'s goals.
  
  == Documentation ==
- TS comes with both an Administration Guide, and a Developer Guide. Work will begin soon
to clean this documentation, and the hope is to move it to our podling web site once activated.
+ TS comes with both an Administration Guide and a Developer Guide. Work will begin soon to
improve this documentation, and the hope is to move it to our podling web site once activated.
  
  == Initial Source ==
- 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.
+ 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 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.
+ 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 sanitized 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.
+ Traffic Server has no external dependencies, other than standard libraries like BDB, OpenSSL,
TCL, STL, glibc and expat.
  
  == Cryptography ==
  Traffic Server uses OpenSSL to implement HTTPS support. There is no other cryptographic
code in the source tree.
@@ -105, +105 @@

  
  == Affiliations ==
  
- All initial developers are employed by Yahoo! Yahoo is also an active user of the Traffic
Server software.
+ All initial developers are employed by Yahoo!. Yahoo! is also an active user of the Traffic
Server software.
  
  == Sponsors ==
  
@@ -115, +115 @@

  === Nominated Mentors ===
  
  === Sponsoring Entity ===
- The Apache Incubator.
+ The Apache Incubator
  

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


Mime
View raw message