I'm writing a (almost) "wizard" web-based project. The base architecture is an Restful service consumed by a web-client that aim to follow the HATOAS approach. Since is a not so lightweight project I'm was thinking of splitting the project in three different SinglePageApplications. For you guys it's a good idea? If so which is the best approach for passing the parameters among the pages? Eg. One page manage a "resource A", you do some basic CRUD operation, then select one of them for the next step: eg. analisys based on object related to "resource A", so you should to pass at least the "resource A" id and maybe some other parameters. Thanks, f
I had a similar project, had to write "Contract Manegement System" for mobile network company, I had login page for 3 type of users - "Admin" , "Manager", "Resposible Person", there were 3 page for these type of users, each of these page represent Single Page Application, that used REST services for interaction with server, and pure JavaScript for passing data into HTML elements, it worked very quickly like desktop application...