Re:Developing Backbone.js Applications
by camus on Thursday December 27, 2012 @04:43PM
(#4975198)
Client side stuffs like validation,etc ... are here only to enhance user experience , you dont want a user to wait til the page reload just to know the password he entered should be at least 6 characters long. Same thing for auth , permissions to access resources are set server-side, and dealt on the client with HTTP response codes. So there is nothing to keep in sync,The server is still free to forbid any resource access, or invalidate granted access.
[ Parent
| on HN ]
Sorry, I didn't mean to imply that the auth stuff needed to be kept in sync, I meant models. People are used to pushing a button and getting a GO / NO GO response of some kind, whereas it seems that with some of these frameworks, people could edit something and have that not show up, if something went wonky in the middle: it's saved "locally", but the ajax request hasn't been completed yet.
Re:Developing Backbone.js Applications
by ricardobeat on Friday December 28, 2012 @12:57AM
(#4976654)
If the request fails a failure notification should be shown, and a rollback to the client model will/can be made.