struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert McBride <rmcbr...@med-access.net>
Subject Re: R: Front Controller?
Date Mon, 07 Jun 2004 22:32:16 GMT
Hi,
Here's a little bit better link about Front Controller.

http://java.sun.com/blueprints/corej2eepatterns/Patterns/FrontController.html

-Rob

Amleto Di Salle wrote:
> Hi,
> Struts contains a Front Controller implementation!
> 
> Anyway, if you want to see the Front Controller design pattern and
> others please visit http://www.corej2eepatterns.com/index.htm
> 
> BR
> Amleto
> 
> 
> 
> 
> 
> -----Messaggio originale-----
> Da: Chaikin, Yaakov Y (US SSA) [mailto:yaakov.y.chaikin@baesystems.com] 
> Inviato: lunedì 7 giugno 2004 18.30
> A: Struts Users Mailing List
> Oggetto: RE: Front Controller?
> 
> 
> 
>>Hi,
>>I think that MVC and Front Controller are slightly different because 
>>MVC (or Model 2) is an "architectural" pattern and Front Controller is
> 
> 
>>a design pattern.
>>
>>Front Controller design pattern is a possible solution for the 
>>Controller "element" inside the MVC pattern.
> 
> 
> Right. So, is there an existing implementation of this somewhere or I
> would have write my own.
> 
> Thanks,
> Yaakov.
> 
> 
>>BR
>>Amleto
>>
>>-----Messaggio originale-----
>>Da: Chaikin, Yaakov Y (US SSA) 
>>[mailto:yaakov.y.chaikin@baesystems.com]
>>Inviato: lunedì 7 giugno 2004 18.13
>>A: Struts Users Mailing List
>>Oggetto: RE: Front Controller?
>>
>>
>>
>>>Model 2 / MVC / Front Controller are all the same thing.
>>
>>Hmm... No, they are not. Front Controller and MVC are similar, but are
> 
> 
>>NOT the same design patterns! Front Controller is used for a sequence 
>>of predefined steps (like a check out on amazon). MVC is used for 
>>separation of Model (data handling), View (presentation handling), 
>>Conroller (where to go). Whatever it is, those 2 design patterns are 
>>not the same.
>>
>>
>>>In Struts the
>>>"Front Controller" is the "ActionServlet", it 
>>>receives/handles/dispatches every single request that comes into 
>>>your web app. You write actions that are like units of 
>>>functionality, then specify in a mapping file the relationship 
>>>between URLs and the
>>
>>Action,
>>
>>>then depending on where the user is going, the ActionServlet will 
>>>call
>>
>>>the appropriate Action at the appropriate time to handle the user's
>>
>>request.
>>
>>Are you suggesting that Struts gives you the ability to specify a 
>>sequence of actions? If so, I am not following how one would do that.
>>
>>>>From what I understand Struts would give you the ability to specify
>>where each action ends up, and in that sense you ARE specifying a 
>>sequence of actions. Is that what you mean?
>>
>>Thanks,
>>Yaakov.
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>>For additional commands, e-mail: user-help@struts.apache.org
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>>For additional commands, e-mail: user-help@struts.apache.org
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Mime
View raw message