> Tapestry applications don't need to have any direct dependencies in the
> Servlet API. If someone implements some HTTP server in Java not based in the
> Servlet API (I guess there must be at least one around), you can adapt
> Tapestry to work on it. Tapestry applications would work out of the box, as
> long as they don't use the Servlet API directly.
You would still need to provide tapestry with replacements for
HttpServletRequest and HttpServletResponse.
I am not sure, but I could imagine that if you try to adapt tapestry
to Simple, you will end up rebuilding a good part of the Servlet API.
That's what servlets are all about: provide an api for developers to
build web apps.
Maybe its just me, but I don't get this whole "dependencies are bad" mindset.
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
