Win a copy of High Performance Python for Data Analytics this week in the Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Jj Roberts
  • Carey Brown
Bartenders:
  • salvin francis
  • Frits Walraven
  • Piet Souris

Thin client Vs thick client

 
Ranch Hand
Posts: 40
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Could anybody give a comparison between thin and thick(SWING) client approach for this application in terms of security, responsiveness, portability, browser compatibility and maintainability

Thanks
Lavanya
 
Ranch Hand
Posts: 236
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You're opening up a religious war here ;-)

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).

Just my $0.02 ...
 
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.

pizazz
Thin
You are limited to what you can pull off with HTML and animated gifs, or Javascript if you cheat on pure thin client.
Thick
What the app does is limited only by your imagination. You have the full power of Java available .

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.
 
His brain is the size of a cherry pit! About the size of this ad:
the value of filler advertising in 2020
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic