Difference between revisions of "Thin Client / Thick Client"
(→Revision Questions) |
(→Revision Questions) |
||
(One intermediate revision by the same user not shown) | |||
Line 50: | Line 50: | ||
||Alright, we get it, you're smart. Shut up. | ||Alright, we get it, you're smart. Shut up. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
{ What is a Thick (Rich) Client server? | { What is a Thick (Rich) Client server? | ||
Line 71: | Line 65: | ||
- False | - False | ||
− | { | + | { The processing in a thin-client network takes place on the the central server. |
− | |type="()"} | + | | type="()" } |
− | + | ||
− | + | + True | |
− | + | + | - False |
− | |||
− | |||
− | |||
− | - | ||
− | |||
− | {What | + | {What are the advantages of a thick client? |
− | |type="[]"} | + | | 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? | { Which is an advantage of a thin client? | ||
Line 116: | Line 101: | ||
||False - a thin client could have greater specifications than a thick client, though it does not necessarily need it. | ||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=" | + | |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. | { In what instances would a thin client be useful to a user. |
Latest revision as of 12:58, 19 November 2019
Contents
Overview
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