Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Thin client vs Fat client exam objectives

 
patrick avery
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Several of the SCJA exam objectives (Section 7: Client Technologies) talk about the pros and cons of various types of thin clients vs fat clients, i.e.

* Describe at a high level the basic characteristics, benefits and drawbacks of creating thin-clients using HTML and JavaScript and the related deployment issues and solutions.

* Describe at a high level the basic characteristics, benefits, drawbacks, and deployment issues related to creating fat-clients using Applets.

* Describe at a high level the basic characteristics, benefits, drawbacks, and deployment issues related to creating fat-clients using Swing.

This is an area I have found difficult to find study material for...maybe somone can suggest some study resources for this?

I did find this link which is excellent, although dated (2001):
http://www.ifi.uzh.ch/ifiadmin/staff/rofrei/DA/DA_Arbeiten_2002/Stock_Mike.pdf

Thanks, Pat
 
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Posts: 4968
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Here's a little something I put on my website to demonstrate applets and the types of things that Swing applications can do. The page has a million applets on it, which slows the page down to a crawl (drawback of fat client?), but it has some good info. It's a place to start!

Fat Client, Swing and Java Applet Clients

-Cameron McKenzie
 
Jason Scarano
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Agreed, I have found nothing on this either. Anybody have any ideas?
 
Ryan Beckett
Ranch Hand
Posts: 192
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
HTML are thin clients because their less resource intensive - its a markup language, no sandbox, no JVM resources - and they provide a less rich set of GUI capabilities, hence the term 'thin'. HTML uses basically forms to send POST data to the server, whereas a applet uses swing and can communicate with a server via Sockets with no page refreshing required.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic