Decoupling web 2.0 applications from server-side implementation
by Amir Shevat
AJAXDO is an example of front-end and server-side decoupling. A full blown standard should include, among other things: security, object passing/storing, some sort of server-side business logic invocation, and even transactions. Now with rise of activity around web 2.0 applications and software-as-a-service concepts it might be a good time to start working on such standards.
What should this front-end and server-side decoupling standard contain?
|The standard must contain a mechanism for backward compatibility between layers (front-end and business).|
So, instead of writing one version of server side code, you write
(and maintain) 2,3...etc.?
And instead of tight control that comes with the code
deployed on server, you mix both the presentation and business logic
and then let it loose on the client?
Don't forget about browser incompatibilities, security issues etc..
I agree with Tom. Ajax is a powerful tool that when used correctly can greatly enhance the web user's experience. Beware however that Ajax is not a panacea. If we load everything up in our presentation layer we will have all-in-one mammoth jsps that will be a hell of a lot harder to maintain.