[undertow-dev] Undertow Status

[Stuart Douglas]

So just a quick update on what we have, and where I think we should be 
going in the near future.

Core Server:

This currently provides basic HTTP/1.1 functionality, which is achieved 
by chaining together various handlers. It has basic support for Cookies, 
Sessions, file serving, form data parsing and a few other things.

I think the short term priorities here should be:
- Add initial SSL support.
- Multipart upload handling - We need a MIME parser that can handle 
Buffers and Channels rather than Streams.
- Improve session handling - The current implementation is very basic)
- Initial security implementation - This is a big topic, I will send an 
email about this to the list shortly

Servlet:

Some basic servlet functionality is implemented, basically Servlets, 
Filters, Listeners and static resource serving. This implementation is 
far from complete though, for example a large number of the methods on 
HttpServletRequest/Response are not functional yet. As much as possible 
this functionality is just a lightweight wrapper around the underlying 
functionality in the core server.

My basic plan here is to try and make servlet functionality, and core 
server functionality required for servlet a priority. Without servlet we 
are unlikely to get any community involvement. Also once we have a 
decent level of servlet functionality we can start TCK testing, which 
will likely show up a lot of issues.

AS7 Integration:

This still early days, but as most of the metadata parsing and 
annotation handling code is the same we can actually deploy and run some 
of the AS7 quick starts (at least helloworld-html5 and helloworld-gwt). 
I think this should also be a priority, as it is required to run Servlet 
apps. As the core deployment code should not change much from what we 
already have I think most of the work here is actually in the management 
side of things.

JSP:
This has not started yet, however as it is necessary for JSF I think we 
should attempt to get basic support up and running sooner rather that 
later. I think the best approach here is to just take our existing JSP 
implementation from JBoss Web. I want to keep this in a separate 
repository, and if possible not tie our servlet implementation to this, 
so we have as little JSP code as possible in the servlet implementation.

Stuart