Serverside Turnkey and MVC functioning
No edit summary
No edit summary
Line 2: Line 2:


=== MVC to Angular Navigation ===
=== 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 need 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 requests on the current page
# MVC Controller receives requests on the current page
# Send redirect to the client to the new page (in MVC)
# Send redirect to the client to the new page (in MVC)
# Requests for this new MVC page redirect to Angular
# Requests this new MVC page to redirect to Angular
[[Category:MDriven Turnkey]]
[[Category:MDriven Turnkey]]
[[Category:MVC]]
[[Category:MVC]]

Revision as of 07:03, 20 October 2023

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
This page was edited 94 days ago on 02/10/2024. What links here