Things AsyncWeb Isn't!

This is the place to highlight and discuss things which AsyncWeb isn't currently designed to do.
If you are thinking "why doesn't AsyncWeb do X?", this might be a good place to start looking!

AsyncWeb Isn't a Web Application Framework

The public API of AsyncWeb is purposely small, and intentionally represents HTTP requests and responses at a fairly low level.
The best way to think about the public AsyncWeb API is as an asyncronous (and cut down) replacement for the Servlet API.

Many users of AsyncWeb will not be using "web application" in the "usual" sense at all. For example, some will require high-throughput SOAP handling, others will simply provide HTTP pass-through.

However, this - by no means - impllies that AsyncWeb isn't design to support web application frameworks - far from it!
I very much hope that support for some existing frameworks will be added to AsyncWeb soon after its release - and that new web application frameworks consider it as a viable HTTP transport mechanism.

It is likely that the feature set of AsyncWeb will evolve as the first web application framework "comes on board" - Im certainly looking forward to the challenge!