Dear all,
I'f committed today in the master the support for abstracting HTTP
stack in lift so that Lift itself does not depend on javax.servlet._
classes. This allows us to add support for Netty, AsyncWeb, etc. or
even your own implementation of a HTTP server etc.
This effort lead to several breaking changes:
1. S.servletRequest is now S.containerRequest, S.servletSession is now
S.containerSession. The reason is that the servlet term seems
inapropriate now as we not necessarily talking about servlets anymore.
2. LiftRules.enableServletSessions is now
LiftRules.enableContainerSessions
I won't enumerate here all methods from the new abstractions but the
traits are:
1. HTTPRequest
2. HTTPResponse
3. HTTPCookie
4. HTTPParam
5. HTTPProvider - This is the entry point in Lift. See how
ServletFilterProvider uses it.
6. HTTPSession
7. HTTPContext
To see how these trait map to JEE servlets world please see
refinements from net.liftweb.http.provider.servlet package
If your application does not explicitly relies on usage on
javax.servlet._ package you should have very little or no changes to
make.
Br's,
Marius