HTTP proxies.

Traffic Server week 1

Traffic Server has been out for a full week now. And it's been great, the interest is huge (almost overwhelming), and surprsingly, lots of people want to participate and contribute. So far, we've already achieved:

  • 64-bit port on Linux!
  • Port to Solaris (and OpenSolaris I believe)
  • Port to Ubuntu (it required a lot of changes due to glibc changes)
  • MacOSX port is partially done.

Not bad for week. If you are interested, check out our Wiki:


TS in the media

Traffic Server is finally here

Finally! We pushed the Traffic Server code to Apache SVN today! This is definitely a momentous occasion, this has been in the works for ages, and it took a lot of work and patience to happen. You wonder, why did we bother? Well, you are right, there's plenty of proxy server alternatives out there, Squid, Varnish, NginX and so on. But, we think we have a platform we can build something on that will be better than anything out there (that is free at least). Why? Well, we have

  • A scalable threaded + asynchronous state machine model. On a typical setup, 2 or 3 threads per core is enough to drive a large amount of traffic.
  • Feature-rich HTTP/1.0 and HTTP/1.1 support. We fair well in various tests like CoAdvisor.
  • Plugin architecture, making it easy (well, easier) to extend and customize your server.
  • Well documented.

I'm not saying it's perfect (far from it), but the hope is that Open Sourcing this will attract an active developer and user community around the software. So, you want more information? Well, besides visiting us on #traffic-server on, here's a bunch of links with some useful information:

Please join the mailing lists (see the Incubator page), talk to us on IRC, or just take a look at the code.

Update: Mark Nottingham (on our team now!) has a blog post with some interesting history and thoughts on TS.



Subscribe to RSS - Proxy