Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: Fat client


Related Topics

In the News (Sat 28 Nov 09)

  
  Client Server   (Site not responding. Last check: 2007-11-06)
Client server computing is a model of computing that involves both user interfaces (individual computers) and a server connected by the network.
These fat clients are labor intensive and expensive to maintain, as they must be updated every time the client software is changed or updated.
Thin clients on the other hand, have changes made on the server side rather than on the system of individual clients.
www.albany.edu /~bn1463/client.html   (202 words)

  
  Client-server - Wikipedia, the free encyclopedia
Clients get all or most of their information and rely on the application server for things such as configuration files, stock quotes, business application programs, or to offload compute-intensive application tasks back to the server in order to keep the client computer (and client computer user) free to perform other tasks.
The interaction between client and server is often described using sequence diagrams.
Another type of client in the Client/Server architecture is known as a thin client, which is a minimal client.
en.wikipedia.org /wiki/Client-server   (587 words)

  
 Thin client - Wikipedia, the free encyclopedia
A thin client is a computer (client) in client-server architecture networks which has little or no application logic, so it has to depend primarily on the central server for processing activities.
On the other hand multicasting entertainment or educational material to a number of clients might best be done with thin clients since exactly the same material is to be presented at each.
Thin client hardware, whether dedicated or simply older hardware that has been repurposed via cascading, is useless or of little interest outside a client-server environment.
en.wikipedia.org /wiki/Thin_client   (1131 words)

  
 Fat client - Wikipedia, the free encyclopedia
In computing, a fat client (also known as a rich client or thick client) is a term from client-server architecture for a client that performs the bulk of the data processing operations.
An example of a fat client would be a Swing (Java) application.
The client may look and behave like a thick client, while being fully network based like a thin client architecture.
en.wikipedia.org /wiki/Fat_client   (172 words)

  
 * Fat Client - (Computing): Definition   (Site not responding. Last check: 2007-11-06)
In a environment, a Fat Client is a client that does the majority of the processing leaving limited work for the server to do.
Fat Client A client/server application that performs most of the processing itself rather than at a server...
A thin client is a network computer without a hard disk drive, whereas a fat client includes a disk drive...
www.mimihu.com /computing/fat_client.html   (146 words)

  
 HTML Paper Submission Guidelines
Clients can then be simpler devices, reducing energy consumption and extending battery life, which is often the primary constraint on the benefits of untethered Internet access with wireless devices.
Similarly, for the fat clients running a web browser, this measurement technique does not account for the time from the moment the client receives the web page data to the moment the page is fully rendered on screen.
For the single-page test, all clients had already established a TCP connection with their respective servers and were awaiting replies from the server before the network was transitioned to a 100% packet loss rate.
www.www2003.org /cdrom/papers/refereed/p741/p741-yang.htm   (9969 words)

  
 Applica Inc.- Zero Client Technology
The zero client ("station") is a set of components (monitor, keyboards, mouse), none of which have independently programmable intelligence, that relies on a centralized CPU ("Host PC") for all program execution and information processing.
Zero client technology has its earliest roots in mini/mainframe computing, where computing tasks and program execution were centralized and information was sent and displayed to multiple users through terminal devices that lacked programmable intelligence, ergo, "dumb terminals" (later renamed "mainframe interactive terminals").
However, the thin client model ignored a crucial change that occurred in the application domain with adoption of Windows as a standard platform: the move from a character-based to a graphical user interface.
www.applica.com /zeroCtech.shtml   (2558 words)

  
 [No title]
Fat Galah will not be responsible for the reconstruction of any lost data, outside of that provided by and required for the operation of Fat Galah itself.
Fat Galah will not be responsible for service interruptions beyond it's control, including but not limited to acts of nature, service interruptions by its providers, or modifications to the client's system by the client or a third party.
Fat Galah reserves the right to discontinue all or any part of the provided service at any time for any reason upon the giving of notice to the client to this effect.
www.fatgalah.com /index.php?PageID=8   (895 words)

  
 The Evolution of Client/Server Computing
The client, a PC or workstation, is the requesting machine and the server, a LAN file server, mini or mainframe, is the supplying machine.
Clients may be running on heterogeneous operating systems and networks to make queries to the server(s).
The fat server approach, using stored procedures is more effective in gaining performance, because the network footprint, although still heavy, is lighter than that of a fat client.
cis.cuyamaca.net /draney/214/web_server/client.htm   (1334 words)

  
 ONJava.com -- Eclipse RCP: A Platform for Building Platforms
Where fat clients tend to be large monolithic applications that are difficult to deploy and update, rich clients are lighter weight and based on a component model that makes them relatively easy to deploy and update.
Historically, fat clients have been built to be platform specific; today's rich-client technologies expose the power of the underlying platform, but hide away the details of that platform, allowing the developer to focus on the task rather than idiosyncratic details of any particular platform.
This limits the environments where fat clients can run (firewalls may restrict connections from the fat client to the database) and the scalability of the application (the total number of connections from the clients to the server) may be limited by the database.
www.onjava.com /pub/a/onjava/2006/08/23/eclipse-rich-client-platform.html   (1352 words)

  
 N-TIER - ARTICLES ~ Client/Server Overview
Much of the processing still occurred on the "fat" clients, but now datasets of information were delivered to the client using Structured Query Language (SQL) techniques to perform requests from a database server, which simply reported the results of queries.
In addition, the network 'footprint' using fat clients, is very large, so that the effective bandwidth of the network, and thus the corresponding number of users who can effectively use the network, is reduced.
The 'fat' Server model, is more effective in gaining performance, because the network footprint, although still heavy, is lighter than the fat Client approach.
n-tier.com /articles/csovervw.html   (1820 words)

  
 Fat vs. Thin: Ten Common Myths about Client / Server | Vital Records | QS Technologies
A “Fat” client is one in which most of the application resides on and runs on the user workstation; a “Thin” client is one where most of the application resides on and runs on one or more server computers.
A fat client could operate with a local database and download data to a host in batches, but it could just as easily be directly connected to a remote database and update in real time.
Since thin clients do less processing on the user’s workstation, they typically are less interactive and therefore have less efficient user interfaces and are harder to use than a well-designed fat client.
www.qstechnologies.com /about/papers/fatvthin.html   (739 words)

  
 OS/2 e-Zine! - You really ought to be using a thin client
Since we have terms like thin client and fat client, the thin client must be less than a fat client, it only stands to reason.
In this context we may find that a fat client, even connected to the network, offers the user far less than a thin client which is not simply connected to the network but is actually managed over the network.
Thin clients need to be repositioned as a superset of a PC by explaining that this is not a connection to the network but an integration with the network.
www.os2ezine.com /v4n7/thinisin.htm   (5875 words)

  
 Bodybuilding.com - Herve Duchemin - How To Properly Train A Female Client For Fat Loss!
The biggest mistake I have repeatedly seen trainers make, is when a female client comes to lose body fat, and winds up training with a trainer who prescribes bodybuilding-type workouts for her, causing her to get big and bulky, rather than small and slender.
In particular, if a client has 50 or more lbs to lose, you will notice that her form will not be "perfect" for most exercises, so you just want to make sure that it is as close to perfect as possible, where the client will not hurt herself.
Remember, if your client is very overweight, you might not be able to see the exact amount of muscle mass she is carrying underneath that fat, so focus more on getting smaller "overall," rather than pushing those pounds and preserving so much muscle.
www.bodybuilding.com /fun/herve8.htm   (2103 words)

  
 Fat Client - Ajax Patterns   (Site not responding. Last check: 2007-11-06)
Fat clients on the otherhand naturally tend to store transient application state information on the browser, and can access server side data with idempotent requests very naturally.
Fat Clients often rely heavily on Rich CSS to provide a rich, desktop-like, appearance.
Where a Fat Client is seen as a replacement for a desktop equivalent, Host-Proof Hosting might be considered to avoid compromising on the superior security a localised solution sometimes offers.
ajaxpatterns.org /Fat_Client   (2947 words)

  
 ShaoLin Microsystems | Products
Clients can even switch back to the original operating system instantly because no disruption is caused to the client's local hard drive.
IUA is a distributed file system technology which automatically separates write-requests from clients, thus each ShaoLin fit client has its own data area (known as host profile) with its specific configurations and hardware drivers.
Fat client PC is an all-in-one design for independent operation.
www.shaolinmicro.com /product/aptus/technology.php   (648 words)

  
 Web-based mail clients still don't measure up
Lotus' release last week of its latest browser-based Notes client again raises the question of whether full-fledged e-mail and collaboration "fat clients" are soon to go the way of the dinosaur.
Although thin clients such as Lotus iNotes Web Access are finding their niche, the promise of a browser-based front end that can match the enterprise worthiness of a native client for corporate messaging and collaboration is no closer to reality than it was when a thin-client revolution was first touted three or four years ago.
The promise of the thin client was that IT would not have to deploy and manage an enormous roster of clients.
www.networkworld.com /news/2001/0716clients.html   (1150 words)

  
 CIO - Sep 1, '96 - Client/Server   (Site not responding. Last check: 2007-11-06)
In a fat client model, every update to the application will require 500 new installations, but in a thin client model-because those 500 desktops will access the application logic located on a single server-only that one server requires updating.
Ryan has found that thin clients are suitable for applications that process simple accounting forms, such as 401(k) retirement plans, but that more complex forms, such as reports for medical insurance, need that fatter client that afford the user more desktop functionality.
By definition, a thin client strips away power from the desktop, and control is a potentially touchy issue in the user-centric world of the personal computer.
www.cio.com /archive/090196/thick.html   (2680 words)

  
 What is fat client? - a definition from Whatis.com
On the other hand, thin clients are more easily managed, are easier to protect from security risks, and offer lower maintenance and licensing costs.
- A fat client (sometimes called a thick client) is a networked computer with most resources installed locally, rather than distributed over a network as is the case with a thin client.
Fat clients are almost unanimously preferred by network users because they are very customizable and the user has more control over what programs are installed and specific system configuration.
searchsmb.techtarget.com /sDefinition/0,290660,sid44_gci1155689,00.html   (323 words)

  
 Thin-Client Computing - Enterprise Applications - Network Computing
In fact, a thin client can accomplish many of the same tasks a fat client can, as long as there are sufficient processors in the SBC setup to satisfy the load from users and applications.
Despite advances in technology and manufacturing that have lowered the cost of fat clients, however, all is not a bargain.
Thin clients are assured of accessing the most recent version of applications installed on servers every time they are connected to the network.
www.networkcomputing.com /showArticle.jhtml?articleID=16101217   (750 words)

  
 Face-off: Thin clients vs. fat clients
Still, the real benefit of fat clients is that they unleash people's minds to do creative -- and productive -- things with technology.
Thin clients are right for some people, and the sea shift that we have witnessed in new applications has made the thin client right for many more corporate users.
The thin client isn't the greatest thing since sliced bread, but it has a role in the corporate world, and we have to think of it as an opportunity -- not the devil.
searchdomino.techtarget.com /originalContent/0,289142,sid4_gci945369,00.html   (2325 words)

  
 Fat client features in a thin client world
The development platform offers an alternative to traditional Web, Microsoft.Net, IBM Websphere and existing thin client technologies and with a client side footprint of around 60kb, is vastly smaller than any equivalent worldwide.
The new SMS client application provides for a traditional "thick client" interface with a Microsoft look and feel user experience including full functionality of a local application, with buttons, tabs, multiple screens or forms and the like.
The system is non-connectioned, in that communications between the Ultra Lite Client and the CellSys Enterprise Application Server only occur once a user commits a transaction by hitting 'enter' on the keyboard.
www.itweb.co.za /office/cell_sys/0306260827.htm   (651 words)

  
 InformationWeek > Carl Zetie > Mobile Architecture: One Size Fits So Few > July 8, 2002
Fat client, thin client, fat client--the debate over mobile-app architectures looks more like the revolving door of a weight-control salon.
Intriguingly, the short history of mobile devices in enterprise IT has rapidly recapitulated this history, having passed through its own fat client and thin client waves, and the current wave of misinformation about the relative network characteristics of fat and thin clients is largely driven by advocates for Web services on mobile devices.
Some have argued that rich clients using Web services are better than thin clients because they don't waste bandwidth transmitting both data and apps as HTML does, while thin-client proponents argue that their model is better because it only has to transmit screen updates, not all of the application data.
www.informationweek.com /story/IWK20020703S0001   (1024 words)

  
 Thin Client Coding Tips
Thin clients are often discussed in the context of three-tier architectures.
This is not to claim the absence of usefulness for thin clients.
For other thin clients, there should be fewer files that need to be installed, along with fewer registry, INI and/or configuration file settings that need to be made.
www.scottnichol.com /thincli3.htm   (2067 words)

  
 Client Server & Thin Client   (Site not responding. Last check: 2007-11-06)
The terms "thin" and "fat" refer mainly to the location where the data and executable program processing is taking place.
If you have a "fat" server, that would mean the server itself is where most all of the processing will be concentrated.
Even though "fat" and "thin" client architectures both have their benefits, the best overall performance by far comes from thin client applications, since far less data and information travels back and forth across the network.
www.timetrak.com /products/thinclient.htm   (830 words)

  
 Thin Client vs. Fat Client – Teil 2
Schlechte Performanz der Anwendung und des GUI Hierbei geht es darum, dass in einer Web-Architektur in der Regel mehr Hintergrundprozesse involviert sind, wenn auf dem Client eine Aktion initiiert wird, was häufig mit einer Laufzeitverlängerung verbunden ist.
Ergonomisch weisen Web-Clients und hierbei vor allem reine HTML-Clients erhebliche Unterschiede zu Fat Clients auf, was zu neuem Lernaufwand bei den Anwendern führt.
Wir glauben, dass der Trend in Richtung dünner Clients geht.
www.contentmanager.de /magazin/artikel_1241_thin_client_fat_client.html   (1667 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.