Serverside Turnkey and MVC functioning
No edit summary
No edit summary
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
See [[Turnkey MVC Controllers]] before reading this article.
<message>Write the content here to display this box</message>
See [[Documentation:Turnkey MVC Controllers|Turnkey MVC Controllers]] before reading this article.


=== MVC to Angular Navigation ===
=== MVC to Angular Navigation ===
Line 10: Line 11:
[[Category:MDriven Turnkey]]
[[Category:MDriven Turnkey]]
[[Category:MVC]]
[[Category:MVC]]
{{Edited|July|12|2025}}

Latest revision as of 05:18, 26 February 2025

This page was created by Lars.olofsson@mdriven.net on 2017-07-03. Last edited by Stephanie@mdriven.net on 2025-02-26.

See Turnkey MVC Controllers before reading this article.

MVC to Angular Navigation

To navigate from MVC to Angular, two EcoSpaces are needed. The existing MVC EcoSpace is handed over to the streaming API. This is due to the need for action continuity, i.e., things done in the MVC action must be available in the AngularJS EcoSpace.

Controller Sequence for MVC to Angular

  1. MVC Controller receives requests on the current page
  2. Send redirect to the client to the new page (in MVC)
  3. Requests this new MVC page to redirect to Angular