Page History

...

An important goal for Tapestry is seamless DHTML and Ajax integration. To serve that goal, it was important that the built in components
be capable of Ajax operations, such as dynamically re-rendering parts of the page. Because of that, it made sense to bundle a well-known JavaScript library as part of Tapestry.

...

Tapestry's Request interface is very close to the standard HttpServletRequest interface. It differs in a few ways, omitting
some unneeded methods, and adding a couple of new methods (such as isXHR()), as well as changing how some existing methods
operate. For example, getParameterNames() returns a sorted List of Strings; HttpServletRequest returns an Enumeration,
which is a very dated approach.

However, the stronger reason for Request (and the related interfaces Response and Session) is to enable
the support for Portlets at some point in the future. By writing code in terms of Tapestry's Request,
and not HttpServletRequest, you can be assured that the same code will operate in both Servlet Tapestry
and Portlet Tapestry.

...