Re:Sammy.js, CouchDB, and the new web architecture
by mcav on Tuesday September 15, 2009 @12:11PM
(#824108)
Good, except that you still have to deal with authentication, authorization, and other security aspects of a server-side component. Server-side code won't go away no matter how fat the client gets.
[ Parent
| on HN ]
Re:Sammy.js, CouchDB, and the new web architecture
by Periodic on Tuesday September 15, 2009 @02:15PM
(#824388)
In this case it will just move into the database. You'll have to start writing procedures and rules in the database instead of in your web framework and only expose those instead having only trusted code interact with the DB.
Re:Sammy.js, CouchDB, and the new web architecture
by mechanical_fish on Tuesday September 15, 2009 @03:37PM
(#824570)
You'll have to start writing procedures and rules in the database instead of in your web framework
This will not fool anyone. You can't fold the business logic into the database and then pretend that you've eliminated the business-logic layer on the server. It's still there. You've just driven it into hiding.
Re:Sammy.js, CouchDB, and the new web architecture
by Periodic on Tuesday September 15, 2009 @03:57PM
(#824603)
Exactly. I don't think there is an equivalence between server code and client code. There are some things you just can't trust the client to do, so there will always have to be server code to do it. Whether that code is in a web server, a framework, a database, it doesn't matter. Someone has to write it.
However, I could see some of the code, such as the code that actually builds the page the users sees, being pushed into the browser. But then, don't we already have that with XML and XSLT (or whatever?)