In the
SCJA exam-objective written by Sun, they call HTML using JavaScript "thin-client" and they call HTML using
Applets "fat-client".
Why? Both JavaScript and Applets are client-side scripting languages. So, both JavaScript and
Java Applets are downloaded from the web-server to the web-client (the web-browser). So why do they call JavaScript "thin-client" and call Applets "fat-client"?
Also, I disagre with Sun calling Swing applications "fat-clients". It seems to me that a Swing application can either be a thin-client or a fat-client, depending upon how the application is implemented. If you choose to use Swing in combination with a
JDBC driver and put the business logic in the app running on the desktop, that is "fat-client", but if you use Swing and use RMI, or Sockets, or JAX-RPC, or you use stored procedures and put the database code on a server, that is "thin-client", right? So a Swing app may be either thin-client or fat-client, right?
Kaydell
[ May 26, 2007: Message edited by: Kaydell Leavitt ]