View source for Thin Client / Thick Client

==Overview==

<youtube>https://www.youtube.com/watch?v=03n1riV0UO8&list=PLCiOXwirraUDUYF_qDYcZV8Hce8dsE_Ho</youtube>

https://www.youtube.com/watch?v=03n1riV0UO8&list=PLCiOXwirraUDUYF_qDYcZV8Hce8dsE_Ho

=Thin Clients=

A thin client is the term used when a dummy pc is used, a network PC without HDD to act as a terminal. This is because the data processing mostly occurs on the server itself. It is also a term used when most of the software of the network pc you are using is on the server itself rather than the pc.
Thin clients require constant server communication to be keep running the way it should.

==Advantages and Disadvantages==

* Easy to deploy requiring no extra or specialised software installations
* Need to validate with the server after data capture
* If the server goes down the collection of the data will go down
* Any workstation can be used on the network to do the same thing
* Reduced security threat

=Thick Clients=
A thick client is the term used when a network pc that does most of its own processing for on the client itself rather than the server like a thin client. It also refers to the fact software is on the PC itself rather than a server. If the applications you are using require multimedia components or are bandwidth intensive a thick client will be much more effective.

==Advantages and Disadvantages==

* Thick clients are much more expensive and require more IT work in the future
* Data verified by client immediately
* Only requires some communication with server
* Reduced server demands
* Increased security issues

=Revision Questions=

<quiz display=simple>
{which of the following apply to thick client network?
|type="[]"}
+most of processing done on device instead of server
|| this is true
+better for multiple devices than peer to peer
|| easier to manage
+less reliant on server than thin client
||thin client almost all processing on server
+well protected from malware
||less reliant on central device so less susceptible and easily backed up and protected

{ True/False: A thick client runs everything through the server, your machine only processes the inputs from the keyboard and mouse.
| type="()" }
- TRUE
|| Naa
+ False
||Alright, we get it, you're smart. Shut up.


{ What is a Thick (Rich) Client server?
| type="()" }
- A client that does no processing.
|| Just cos it's rich doesn't mean it can't do work.
+ A client that does all its own processing.
||Alright, we get it, you're smart. Shut up.
- A slightly overweight server.
||...??

{Thick Client is when all of the processing takes place on the client machine
|type="()"}
+ True
- False

{ The processing in a thin-client network takes place on the the central server.
| type="()" }

+ True
- False

{What are the advantages of a thick client?
| type="[]" } 
+ Better data and program processing
+ Can work offline
- Less security vulnerability
- It is more cost effective

{ Which is an advantage of a thin client?
| type="()" }
- much more expensive and require more IT work in the future
|| You big dumb dumb
+ Easy to deploy requiring no extra or specialised software installations
|| Yeah alright u got it, stop braggin about it.
- If the server goes down the collection of the data will go down
|| Thats a disadvantage. What is wrong with you?
- None of the above
|| bruh

{Which of the following are true for thin clients?
| type="[]"}

+Applications are stored on the server rather than the client
||True, thin clients do not have applications installed on them; processes occur on the server.
-Devices are operable without a connection to the network / server
||False, the opposite is true.
+Thin clients require a connection to the network
||True, as otherwise they are inoperable
-Thin clients always have lower specifications than a thick client
||False - a thin client could have greater specifications than a thick client, though it does not necessarily need it.

{What is a dumb terminal and when is it used?
|type="[]"}
+ Used with thin clients.
| Yes
- Used with thick clients
| No
- A terminal that doesn't work for it's intended function
| No
+ A PC lacking in certain pieces of hardware, but can still form an input and output
| A dumb terminal is used to access software on thin clients, they don't need as much hardware as a normal PC because most/all processing is done on the server.


{ In what instances would a thin client be useful to a user.
| type="[]" }

+ When using a device with very low processing power.
- When trying to run a video game directly from the device.
+ To act as a highly secure dummy, between other clients and the server,
- To process tasks while moving around offline.

</quiz>