Re: [Phrame-devel] Use of session...

[Tony B. <to...@to...>]

On Thu, 6 Mar 2003, Arnold Cano wrote:

> I do prefer having a single mechanism for handling
> views (a special action).  I did a lot of research
> determining if push or pull mvc would be a better
> approach to take and found this article:
> 
> http://www.ingrid.org/jajakarta/turbine/en/turbine/turbine-2/pullmodel.html
> 
> I'm not sure about the idea of combining actions with
> forms.  The original idea behind keeping them separate
> is that the action mechanism (the command pattern)
> should only be concerned with handling command logic. 
> Keeping the forms separate from this enabled the
> framework to validate form data before an action was
> even involved in the process of handling the request
> and allowed for form reuse between actions.

I think we are arguing over semantics.  You could have a base abstract 
object that both the action and form object inherit from.  Call it what 
you want.  In the end, the separation you are seeking between the 'action' 
and the 'form' is really more logical.  Again the real value is the fact 
you now have the display portion of a view tied to the validation in one 
object.

> 
> I like the idea of creating a secure action.  We
> should also create other useful base actions such as a
> DispatchAction that would allow the use of ACID
> methods in a single action through the use of the
> _PARAMETER action mapping attribute.

Good!

> 
> There are many places that refactoring could happen
> and I agree that we should implement the use of
> factories for the actions, mappings, forms, and
> forwards.  The use of the session to hold the
> controller is not required and I think changing it to
> use a static variable (the singleton pattern) is a
> great idea.

Great!

--Tony