[ACCEPTED]-What do you mean by thin-client application?-thin-client

Accepted answer
Score: 13

A thin client application is one where the 57 requirements on the user-side application 56 host, in terms of processing power, footprint 55 and configuration are relatively minimal.

Thin 54 client applications are opposed to applications 53 which require the end-user side to do some 52 of the following:

  • install an application-specific program, typically a relatively big binary, maybe with dependant libraries and supporting files,
  • install a database of sorts
  • include its own logic to process some of the functions of the appliciton, end-to-end.

Such "non-thin client" applications 51 do not exclude the possibility of having 50 some of the data or features of the application 49 served from a remote server, but several 48 of the applications features are handled 47 locally by the application.

Thin clients 46 on the other hand imply the existence of 45 a server which provides most of the application's behavior, leaving the "thin-client" side 44 handle little more than input from the end-user 43 and display on the screen.

A web application is in most 42 cases a thin-client application, even though 41 it is not always thought as such (because 40 the 'thin client' term was traditionally 39 used in the context of terminal services 38 (see below)). The web browser does little 37 more than these User Input / Display functions 36 (even though doing some of this requires 35 a bit of javascript heavy lifting). With 34 the arrival of "Web 2.0" and its 33 web browsers with fast and reliable javascript, html5 32 features such as canvas, etc.the distinction 31 between web applications and thin-client 30 may become blurred again. On the whole, because 29 of their heavy server support these applications, and 28 because of their ability to "just work" (no 27 client-side installation required) web applications 26 will be considered 'thin client', I think, even 25 when the client receives big scripts so 24 it can support several features locally...

There 23 are many applications which are not web-browser 22 based and which qualify as thin-client. For 21 example a dedicated online ordering application 20 that would let the end-user search former 19 orders or the catalog itself, input new 18 orders with some minimal validation etc. would 17 qualify as thin-client.

A technology often 16 associated with thin client is that of Microsoft's 15 Terminal Services (or simlar technologies offered by other 14 vendors such as Citrix), whereby the end-user 13 side computer is merely a graphic console, taking 12 input from the end user and passing it 11 along to the server, and receiving exact 10 bitmap images of the portions of the screen 9 that need to be updated. This technology 8 allows running unmodified traditional applications, on 7 the server side, and have these used on 6 any thin client that may need it. In this 5 fashion, no installation is required on the client side, and 4 also the hardware requirements for the client-side are much 3 reduced, since all of the heavy calculations, access 2 to huge storage and other expensive resources 1 are done by the server.

Score: 13

Thin client application is where all the 5 business logic on server side, but very 4 little code is on client side as we can 3 see in web applications where very little 2 code available in javascript but all the 1 processing logic is in server,

Score: 5

A thin client is the one where it just acts 3 as an interface to the user. The whole business 2 processing is done at the server end where 1 the server application is hosted.

Score: 3

A thin client can refer to either a software program or to an actual computer that 12 relies heavily on another computer to do most of its work. A thin client is 11 part of a network, and the client software 10 or computer acts as an interface, while 9 the network server computer does all the 8 real work. In the case of a computer, a 7 thin client is unable to perform many functions 6 on its own. A thin client computer may be 5 a machine designed only for online use, sending 4 and receiving email, and surfing the net. A 3 thin client computer may also be part of 2 a larger network, at a company or school 1 for example.

Read more here

What is a Thin Client?

Score: 1

Means client side application which consumes 17 low system resources. Resources can be - RAM, Hard 16 disk, graphic processing power and similar 15 other. And it relies on server(can be other 14 computer) to fulfill part of resource requirement.

Examples of 13 thin client application:

Browser: provides a common 12 platform for thin client applications to 11 run. As only browser needs needs to be installed 10 on client side its the most popular way 9 to create thin client application, only 8 downside is not much privileges are provided 7 for application to run.

Some online services 6 like weather service: Not each computer can connect to 5 satellite to know weather conditions (and 4 probably not feasible), so installed application 3 can connect to common server which in turn 2 communicate with satellite and return the 1 result to application.

Score: 1

A thin client typically means that the server does 2 the majority of the work, while the client 1 application does very little.

Score: 1

A thin client can refer to either a software 14 program or to an actual computer that relies 13 heavily on another computer to do most of 12 its work. A thin client is part of a network, and 11 the client software or computer acts as 10 an interface, while the network server computer 9 does all the real work. In the case of a 8 computer, a thin client is unable to perform 7 many functions on its own. A thin client 6 computer may be a machine designed only 5 for online use, sending and receiving email, and 4 surfing the net. A thin client computer 3 may also be part of a larger network, at 2 a company or school for example.

Read more 1 here

Score: 0

The traditional thin client is the terminal/mainframe 5 model. The terminal exists only to relay 4 instructions to the mainframe and present 3 a meaningful UI to the user. A good modern 2 example is the web browser and the web server 1 (with the browser being the thin client).

Score: 0

This is a bit of a crude explanation as 12 there's more to it, but in simple terms 11 I like to think of it like this:

If you're 10 building software that is some variance 9 of the following pattern:

UI -> domain model 8 -> data

Then, in a thin client the UI layer 7 is on the client machine (think of html 6 pages, pre heavy javascript) and everything 5 else is in a separate location (a server 4 in many cases)

Whereas a thick client is 3 where the data is on the [server] and the 2 UI and domain model/logic is on the machine 1 (think client side scripting/logic).

Score: 0

Typically referred to a web application.


Score: 0
  • Thin client is browser based application.
  • Thick client is OS based application.

Basically, a thin client is a web based 9 application and most of the processing is 8 done on the server side.

A thick client is 7 installed into the client side. It is still 6 connected to the server, but most of the 5 processing is done on client side. With 4 thick client, there won't be much processing 3 via the network. In a way, it will be a 2 much faster option if your network is slow 1 or congested.


More Related questions