> it would be the controller.
> If it is the controller. Would you say that it acts like a
> traffic cop and directs all the MVC calls?
The order in which circuits are called is determined by you the coder. For
isntance: in your fusebox.xfml.cfm file you have defined all your circuits
(here is an example I am working on now...):
<!-- MODEL CIRCUITS (PRIVATE CIRCUITS) -->
<circuit alias="mMain" path="_Model/Main/" parent="" />
<circuit alias="mSecurity" path="_Model/Security/" parent="" />
<circuit alias="mUser" path="_Model/User/" parent="" />
<!-- VIEW CIRCUITS (PRIVATE CIRCUITS) -->
<circuit alias="vMain" path="_View/Main/" parent="" />
<circuit alias="vSecurity" path="_View/Security/" parent="" />
<circuit alias="vUser" path="_View/User/" parent="" />
<!-- CONTROLLER CIRCUITS (PUBLIC CIRCUITS) -->
<circuit alias="main" path="_Controller/Main/" parent="" />
<circuit alias="security" path="_Controller/Security/" parent="" />
<circuit alias="user" path="_Controller/User/" parent="" />
The controller acts like a "policeman"; calling the appropriate MODEL and
VIEW circuits to complete the request for a specific fuseaction.
For example: user.showLogin
Since "user" is mapper to _Controller/User/ that is the first circuit file
to be dealt with
So, inside that _Controller/User/ circuit you would have
<fuseaction name="user.showLogin" permissions="">
<do action="" />
</fuseaction>
Then the next circuit.xml.cfm file to be processed is the circuit inside the
_View/User which includes the form
<fuseaction name="loginForm" permissions="">
<include template="frm_login.cfm" />
</fuseaction>
All request should go through the CONTROLLER who will then access the MODEL
and VIEW.
HTH,
Mike
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
