Spending a week in San Francisco working with engineers from Apple, Google, Mozilla, Yahoo, AOL and a bunch of smaller but no less talented outfits. Awesome.
So milton's licensing structure is a bit weird. Thats the result of a few years of ongoing compromise between conflicting requirements between being as open as possible, while still earning enough income to remain a healthy project. In this article I'll explain how the licensing works, and why its the way it is.
So i hit the limit of what you can do with tomcat with my cloud based web development product, and made the decision to switch to Grizzly. I needed SNI support, with user configurable SNI, and buffered uploads were a real problem Milton has always had a strong abstraction away from the servlet api meaning that any http server can be plugged in. I've just got that up and running and have contributed the main parts of the integration to milton, and will walk you through it in this article.