Saving data is simple, right? What app isn't complete without some sort of saving mechanism? And while I'm at it, it's nice to be able to track when changes occur so I can tell if a user can press the save button or even leave the current screen. Which bring me to making my buttons smart enough to know that they are already involved in a asynchronous process, so commanding would be nice. Finally, if I want to save data, it might be a good idea to validate the input on the client (and the server). There are a lot of moving parts involved with saving changes, and I cover these in my new Pluralsight course "Single Page Apps with HTML5, ASP.NET Web API, Knockout, and jQuery". You can catch up on the previous posts ...
Go to the complete details ...