3 ms·
You design your application as if it were to run in a server but... but... it runs in the client. Nice idea. I wonder how this could interact with a nodejs imp
by jhrobert 16y ago
You design your application as if it were to run in a server but... but... it runs in the client.
Nice idea. I wonder how this could interact with a nodejs implementation on the server side.
- Tichy 16y agoI am not sure if this is actually the best way to design an application, or if it is just that we are so used to it by now. Seriously, not sure.
- raganwald 16y agoI'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.
- Tichy 16y agoGood point, that makes a lot of sense.
- mcantelon 16y agoYou could have node.js serve different feeds of JSON data (or just use node.js for whatever you need realtime, via socket.io, and pull the JSON from an old-school CMS).