I'm using Sammy right now and so far I have two responses to the question of whether a client application should be designed as if it were a server application.
The first thing is that if you are going to run in a browser, I see it as a benefit to have an application where natural navigation "places" have bookmarkable, back buttonable URLs. Sammy makes that easy.
As for the "rest," you don't need to have anything to do with posts and forms and making things rest-ful if you don't want. Sammy ships with a storage plug-in and you can go to town making a state-ful application.
However, if you do want to sup[port book-marks and the back button, you want to give some thought to the relationship between applications state and URLs.
The first thing is that if you are going to run in a browser, I see it as a benefit to have an application where natural navigation "places" have bookmarkable, back buttonable URLs. Sammy makes that easy.
As for the "rest," you don't need to have anything to do with posts and forms and making things rest-ful if you don't want. Sammy ships with a storage plug-in and you can go to town making a state-ful application.
However, if you do want to sup[port book-marks and the back button, you want to give some thought to the relationship between applications state and URLs.