• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Is a client that uses PL/SQL considered to be thin or fat?

 
Ranch Hand
Posts: 701
2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

If a client uses PL/SQL it can be considered to be thin or fat? Why?
 
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
'Thin client' is by definition client with all business logic processed on server side. If all business logic is defined in PL/SQL and client is limited to displaying obtained results, I would say it is thin client.
 
Ranch Hand
Posts: 271
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Would that depend on how much more the client does? Wikipedia says :

A fat client or rich client is a computer (client) in client-server architecture networks which typically provides rich functionality independently of the central server. Originally known as just a 'client' or 'thick client', the name is derived from thin client, describing a computer which heavily depends on a server's applications.



So it could be that the client uses PL/SQL (which typically resides in your RDMS) but still does heavy work on its side, then that client would be fat or hybrid
[ November 27, 2008: Message edited by: jeff mutonho ]
 
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Definitely this is fat client.

This is exactly what we call "client" traditionally.

When we talk about "thin" client nowadays, we really means browser based client.

Cheers,
Tao
 
Michael Wiezik
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Lann Lu:
Definitely this is fat client.

When we talk about "thin" client nowadays, we really means browser based client.

Cheers,
Tao



I would not agree with that, I would call rich-GUI Swing client with all business logic processed as PL/SQL still a 'thin' client. I would not call application defining a presentation logic a 'fat client'. But overally, I don't think it makes sense to argue where exactly is border between fat and thin client. On one end, you've got thin clients, classic terminals that just display output generated by mainframe server and forward all key events to it. On the other end, you've got unarguably fat clients, desktop applications, performing SQL queries / updates directly on database. But in the middle, you've got full spectrum of applications like ajax-based text editors, applets, and mentioned swing->psql clients which do not classify that easily.

You could also argue that thin clients by definition do not require updates on client-side, but again, with technologies such as Java Web Start even that classifier is sometimes ambiguous.
 
Lann Lu
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi, Michal,

I understand your point exactly.

But terms are formed by the industry, not by our understanding.

Again "Thin" client specifically refers to web based client in past 10 years, the concept may evolve though.

Anyway it doesn't matter what we call it, I believe our understandings are the same.

Cheers,
Tao
 
Lann Lu
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi, Michal,

I understand your point exactly.

But terms are formed by the industry, not by our understanding.

Again "Thin" client specifically refers to web based client in past 10 years, the concept may evolve though.

Anyway it doesn't matter what we call it, I believe our understandings are the same.

Cheers,
Tao
 
Lann Lu
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Sorry, double click issue happened.

Tao
 
jeff mutonho
Ranch Hand
Posts: 271
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Lann Lu:
Hi, Michal,



But terms are formed by the industry, not by our understanding.

Again "Thin" client specifically refers to web based client in past 10 years, the concept may evolve though.


Cheers,
Tao



Not necessarily.It might just be that WE have limited our understanding of the term to web based clients due to the nature of our work (which focuses on building such type of apps..ie web apps), but as these examples on this Wikipedia article show , the usage goes beyond web based clients...even in the past 10 years.

http://en.wikipedia.org/wiki/Thin_client#Examples_of_thin_client_and_thick_client_usage
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
A good topic for discussion, web-based clients are always designed to be thin clients. Even you can design a swing based application to be a thin client.

The design of your application defines where the busniess/logical processing will be handled or communication with the DB / other applications will be handled, which would clearly describe the type of client your application is.
[ December 15, 2008: Message edited by: Abhilash Muralidharan ]
reply
    Bookmark Topic Watch Topic
  • New Topic