My own strong preference has generally been for "thin" bindings: "less is more".
In my experience, however, well-engineered "thick bindings" have typically enjoyed the most popularity and had the biggest successes - especially when it comes to bindings for Object Oriented languages (like Java).
Hey! These are some of the difference i studied a long back from googling the net. Correct me if i am wrong and add more if i missed out anything.
Java Thin Java runs only on the server. Thick Java runs on client and server.
browser Thin Required. Thick Optional. You can run the client portion as an Applet in the browser, or stand-alone without the browser. Getting rid of the browser gives you back RAM.
Speed Thin Slow. Everything must wait for the server to process and transmit the next screenful of information. Thick Fast. Can instantly scroll especially if the app caches data locally. However, starting the application is slower than with thin client.
editing Thin Edits are done in block mode. You don't find out about your errors until you hit submit. Thick You find out about an error the instant you key it, or sometimes as soon as you finish keying a field. The cursor is placed on the exact source of the error.
hassle Thin You must do all your coding on a server. If you don't own a server, you will have a hard time espicially when you would like to debug. Thick You do some of your coding on the server and some on the client. This makes more flexibility, also you can debug your client stand alone application.
JebaRaj.<br /> MCP, SCJP 1.5 <br />----------------------------<br /> THOUGH TIMES TEACH TRUST. <br />----------------------------
His brain is the size of a cherry pit! About the size of this ad: