--- "PILGRIM, Peter, FM" <[EMAIL PROTECTED]> wrote:
-----Original Message----- From: David Graham [mailto:[EMAIL PROTECTED]
--//--
I chose my words carefully when I said "ActionContext interface". I
*think* we can all agree that if we added this it should be an interface
:-).
--////--
Why would want the ActionContext to be an interface?
Well, ServletContext is an interface and it makes sense for this to be an interface rather than an unnecessarily limiting base class.
--//--
I presume that there would be default implementation , then. What I am getting at here, this default implementation could be extended by normal web application developers, say to add in security profile information.
Non-trival web application, say framework developers like myself, would write implementation of the interface. In Expresso there are two contextes ( ControllerRequest and ControllerResponse) abstractions of the web servlet request and servlet response. We can write controller that run outside of the web app environment. I think this is where you are going with the ActionContext interface.
If the interface was supposed to be environment free what would this interface be?
--
Peter Pilgrim
__ _____ _____ _____
/ //__ // ___// ___/ + Serverside Java
/ /___/ // /__ / /__ + Struts
/ // ___// ___// ___/ + Expresso Committer
__/ // /__ / /__ / /__ + Independent Contractor
/___//____//____//____/ + Intrinsic Motivation
On Line Resume
||
\\===> `` http://www.xenonsoft.demon.co.uk/no-it-striker.html ''
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
