Why is it called Antiweb?
When the first generation of Antiweb was written, almost everybody was using process or thread per connection webservers. Rather than just follow what everyone else was doing, we were going to do our own thing and be the anti-web. So in 1999 we released awhttpd 2.0, an asynchronous select-based server. A couple years later, we released awhttpd 3.0, another select-based server that served us well for years. Today with servers like nginx and lighttpd, asynchronous servers are commonplace. But if you look closely at Antiweb you will notice that it is still quite different from most other servers. We like where we are going and hope you will too.
