Le nouveau contrôleur, qu’on appellera Row, contiendra les actions relatives aux Modèles dans la tableView tandis que index.js (l’ancien contrôleur) s’occupera des actions sur la window et la collection.
à bientôt pour une suite à ce tuto qui ajoutera un peu de style (personnalisation selon l’OS), de la gestuelle, des menus et une synchronisation via services REST.
SPA (Single Page Applications) are web applications commonly developed in HTML, JavaScript and CSS. The user loads the initial page then all the needed resources are loaded dynamically via XHR and inserted into the DOM without reloading the page.
Developing SPA application can be extremely exciting, but we should always stay focused on securing all the app’s possible leaks.
Managing user authentication via RIA (Rich Interface Applications) is similar to standard web Client Server Application. Usually, in Standard web apps the authentications is fully managed by the used framework (Laravel Auth, Spring Security …) and it’s pretty simple:
After a valid user authentication, the server sends a secret token that is stored server side in the
Server Session or the DataBase, and client side in the cookies.
Each time the client (browser) asks for a resource, it sends the secret token in the header.
The server compares the token with the one it has, if it’s valid, it responds and sends back a new token that will be used for the next request.
If there is a problem with the token the user is redirected to the Login form.
RIA apps uses XHR requests to retrieve data from the server via REST services, it can’t manage authentication exceptions, because the tokens verification are made server side.
In our case we will be developing a REST API that should use the Framework Authentication features and manage Authentication issues (disconnects, session expiry, hacks, etc …) and redirect the user to the login form.
andulkaphoto
romaincrisis
snowghoul
discoholicmusic
janainaart