Documentation:Serverside Turnkey and MVC functioning: Difference between revisions

Serverside Turnkey and MVC functioning

Latest revision as of 07:56, 17 June 2024

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

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

This page was edited 95 days ago on 06/17/2024. What links here

@@ Line 1: / Line 1: @@
+<message>Write the content here to display this box</message>
 See [[Turnkey MVC Controllers]] before reading this article.
-=== MVC to Angular navigation ===
+=== MVC to Angular Navigation ===
-When navigating from MVC to Angular, two EcoSpaces are needed. The existing MVC EcoSpace is handed over to the streaming API. This is done because of the need for action continuity, i.e. things done in the MVC action needs to be available in the AngularJS EcoSpace.
+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 ====
+==== Controller Sequence for MVC to Angular ====
-# MVC Controller receives request on current page
+# MVC Controller receives requests on the current page
-# Send redirect to client to the new page (in MVC)
+# Send redirect to the client to the new page (in MVC)
-# Request for this new MVC page, redirects to Angular
+# Requests this new MVC page to redirect to Angular
+[[Category:MDriven Turnkey]]
+[[Category:MVC]]
+{{Edited|July|12|2024}}