Well,

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 just a "client", or "thick-client" in the early days of PC based computing, the word "fat" is in opposition to the "thin" within thin-client, however it typically means that the size of the application which resides on the client machine is large (although browsers such as Internet Explorer, within thin-clients, are often far bigger).

A fat client still requires at least periodic connection to a network or central server, but is often characterised by the ability to perform many functions without that connection (consider a fat mail client such as Microsoft Outlook compared to a thin-client-based mail system such as Hotmail).

It is also usually characterised by a requirement to install a specific application.

In contrast, a thin client generally does as little processing as possible and relies on accessing the server each time input data needs to be processed or validated.


fat server:-

A server in a client/server environment that performs most or all of the application processing with little or none performed in the client. The counterpart to a fat server is a thin client.

Answered by ajay kumar , an ibibo Master, at 5:36 AM on May 12, 2008

well shashi 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 just a "client", or "thick-client" in the early days of PC based computing, the word "fat" is in opposition to the "thin" within thin-client, however it typically means that the size of the application which resides on the client machine is large (although browsers such as Internet Explorer, within thin-clients, are often far bigger).

A fat client still requires at least periodic connection to a network or central server, but is often characterised by the ability to perform many functions without that connection (consider a fat mail client such as Microsoft Outlook compared to a thin-client-based mail system such as Hotmail). It is also usually characterised by a requirement to install a specific application.

In contrast, a thin client generally does as little processing as possible and relies on accessing the server each time input data needs to be processed or validated.

Answered by laks , an ibibo Master, at 4:30 PM on May 10, 2008

well, Fat client is a computer (client) in client-server architecture networks which typically provides rich functionality independently of the central server. Originally just a "client", or "thick-client" in the early days of PC based computing, the word "fat" is in opposition to the "thin" within thin-client, however it typically means that the size of the application which resides on the client machine is large (although browsers such as Internet Explorer, within thin-clients, are often far bigger).
A fat client still requires at least periodic connection to a network or central server, but is often characterised by the ability to perform many functions without that connection (consider a fat mail client such as Microsoft Outlook compared to a thin-client-based mail system such as Hotmail). It is also usually characterised by a requirement to install a specific application.

In contrast, a thin client generally does as little processing as possible and relies on accessing the server each time input data needs to be processed or validated.Introduction
A server in a client/server environment that performs most or all of the application processing with little or none performed in the client. The counterpart to a fat server is a thin client.

Answered by Saurabh , an ibibo Master, at 11:00 PM on May 05, 2008

hi shashi:-
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 just a "client", or "thick-client" in the early days of PC based computing, the word "fat" is in opposition to the "thin" within thin-client, however it typically means that the size of the application which resides on the client machine is large (although browsers such as Internet Explorer, within thin-clients, are often far bigger).

A fat client still requires at least periodic connection to a network or central server, but is often characterised by the ability to perform many functions without that connection (consider a fat mail client such as Microsoft Outlook compared to a thin-client-based mail system such as Hotmail). It is also usually characterised by a requirement to install a specific application.

A server in a client/server environment that performs most or all of the application processing with little or none performed in the client. The counterpart to a fat server is a thin client. Contrast with fat client. See two-tier client/server.

Answered by shepherd , an ibibo Master, at 7:02 PM on May 05, 2008

fat client is a computer (client) in client-server architecture networks which typically provides rich functionality independently of the central server. Originally just a "client", or "thick-client" in the early days of PC based computing, the word "fat" is in opposition to the "thin" within thin-client, however it typically means that the size of the application which resides on the client machine is large (although browsers such as Internet Explorer, within thin-clients, are often far bigger).

A fat client still requires at least periodic connection to a network or central server, but is often characterised by the ability to perform many functions without that connection (consider a fat mail client such as Microsoft Outlook compared to a thin-client-based mail system such as Hotmail). It is also usually characterised by a requirement to install a specific application.

In contrast, a thin client generally does as little processing as possible and relies on accessing the server each time input data needs to be processed or validated.
A server in a client/server environment that performs most or all of the application processing with little or none performed in the client. The counterpart to a fat server is a thin client.

Answered by Smarty , an ibibo Master, at 5:24 PM on May 05, 2008

shashi FAT client is In a client/server architecture, a client that performs the bulk of the data processing operations. The data itself is stored on the server. See thin client for contrast.
Although the term usually refers to software, it can also apply to a network computer that has relatively strong processing abilities
and FAT server is A server in a client/server environment that performs most or all of the application processing with little or none performed in the client. The counterpart to a fat server is a thin client

Answered by raj u , an ibibo Master, at 3:27 PM on May 05, 2008

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 just a "client", or "thick-client" in the early days of PC based computing, the word "fat" is in opposition to the "thin" within thin-client, however it typically means that the size of the application which resides on the client machine is large (although browsers such as Internet Explorer, within thin-clients, are often far bigger).

A fat client still requires at least periodic connection to a network or central server, but is often characterised by the ability to perform many functions without that connection (consider a fat mail client such as Microsoft Outlook compared to a thin-client-based mail system such as Hotmail). It is also usually characterised by a requirement to install a specific application.

In designing a client-server application, there is a decision to be made as to which parts of the task should be done on the client, and which on the server. This decision can crucially affect the cost of clients and servers, the robustness and security of the application as a whole, and the flexibility of the design to later modification or porting.

The characteristics of the user interface often force the decision on a designer.

For instance, a drawing package could choose to download an initial image from a server and allow all edits to be made locally, returning the revised drawing to the server upon completion. This would require a thick-client and might be characterised by a long time to start and stop (while a whole complex drawing was transferred) but quick to edit.

Conversely, a thin client could download just the visible part(s) of the drawing at the beginning and send each change back to the server to update the drawing. This might be characterised by a short start-up time, but a tediously slow editing process.

Answered by Hem@nt , an ibibo Master, at 10:45 AM on May 05, 2008

well shashi,A fat client is a computer (client) in client-server architecture networks which typically provides rich functionality independently of the central server. Originally just a "client", or "thick-client" in the early days of PC based computing, the word "fat" is in opposition to the "thin" within thin-client, however it typically means that the size of the application which resides on the client machine is large (although browsers such as Internet Explorer, within thin-clients, are often far bigger).

A fat client still requires at least periodic connection to a network or central server, but is often characterised by the ability to perform many functions without that connection (consider a fat mail client such as Microsoft Outlook compared to a thin-client-based mail system such as Hotmail). It is also usually characterised by a requirement to install a specific application.

In contrast, a thin client generally does as little processing as possible and relies on accessing the server each time input data needs to be processed or validated.
A server in a client/server environment that performs most or all of the application processing with little or none performed in the client. The counterpart to a fat server is a thin client.

Answered by Uttam , an ibibo Master, at 10:27 AM on May 04, 2008

Fat Client
* Fat clients are the more traditional form of client/server.
* The bulk of the application runs on the client side of the equation.
* In both the file server and database server models, the clients know how the data is organized and stored on the server side.
* Fat clients are used for decision support and personal software.
* They provide flexibility and opportunities for creating front-end tools that let end-users create their own applications.
Fat Server:
* Fat Server applications are easier to manage and deploy on the network because most of the code runs on the servers.
* Fat servers try to minimize network interchanges by creating more abstract levels of service.
* Transaction and object servers, for example, encapsulate the database.
* The client in the fat server model provides the GUI and interacts with the server through remote procedure calls (or method invocations)
* These are used for mission-critical applications, represent the new growth area fro PC-based client/server computing.

Answered by jaivir , an ibibo Master, at 9:12 AM on May 04, 2008

A user's computer that contains its own applications that are run in the machine. New programs are installed on the local hard disk.
A server in a client/server environment that performs most or all of the application processing with little or none performed in the client. The counterpart to a fat server is a thin client.

Answered by Kajal Sharma , an ibibo Master, at 8:41 PM on May 03, 2008