on 9/22/2000 6:22 AM, "Rafal Krzewski" <[EMAIL PROTECTED]> wrote:
> Nicola Muratori wrote:
>
> That's simple - run data holds the information that is
> needed for processing a single http hit. The session
> holds information that persists over multiple hits.
>
> Rafal
To add to this...it is the way that the Servlet API should have been
implemented in the first place and is how I will propose to create Servlet
API 3.0 someday in my not-so-spare-time. :-)
Passing around HttpRequest/HttpResponse objects in every single method was a
bad non-OO way of doing things. They should have been put into a single
container object.
If you notice, HttpSession is what is IN RunData. It is the other way around
that is correct. :-)
Think of Turbine as being my view of how the Servlet API should have been
created in the first place. :-)
-jon
--
http://scarab.tigris.org/ | http://noodle.tigris.org/
http://java.apache.org/ | http://java.apache.org/turbine/
http://www.working-dogs.com/ | http://jakarta.apache.org/velocity/
http://www.collab.net/ | http://www.sourcexchange.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
