Server side and client side processing Flashcards

1
Q

What is server side processing

A

when a client sends data to a server for it to be processed. This
means no information is processed on the client computer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Common server side processing languages

A

SQL or PHP

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Why is server side processing useful

A

● Does not require plugins
● Can perform large calculations much faster than clients
● Not browser dependent,
● More secure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is client side processing

A

when a client processes the data on a local device. This means
that all of the information is processed on the client computer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Why is client side processing useful

A

● Webpage can immediately respond to user actions
● Executes quickly
● Gives developers more control over the behaviour and look of the website

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Where does client side processing take place

A

Web browsers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Where does server side processing take place

A

on the
webserver. Data is sent from the browser
to the server, the server processes it and
sends the output back to the browser

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What does client side processing not require

A

Data to be sent back and forth meaning code is much more responsive

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Is code visible or invisible with client side processing

A

Code is visible which means it can be
copied

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What does server side processing take away

A

the
reliance of the browser having the correct
interpreter

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Is code invisible or visible to the user with server side processing

A

It hides the code from the user,
protecting copyright and avoiding it being
amended/circumvented

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Disadvantage of server side processing

A

Server side
processing puts extra load on the server.
This is at the cost of the company hosting
the website

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

When is client side processing best used

A

Client side processing is best used when
it’s not critical code that runs or where a quick response is needed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

When is server side processing best used

A

Server side processing is best used where
it is integral that processing is carried out.
It is often used for generating content or accessing secure data

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are the Get and Post requests?

A

The two main types of HTTP request. Get requests are supposed to be harmless and repeatable and can be bookmarked. Post requests are for when a change is meant occur (e.g. create, update or destroy operations).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is the URL (Uniform Resource Locator)?

A

A text string that represents a destination for a HTTP (or other protocol) request.

17
Q

How does javascript allow dynamic web pages

A

Modern JavaScript can execute HTTP requests without the need to reload the page. This makes it possible to create dynamic web applications

18
Q

Uses of server side processing on the web

A

Accessing a database
Security and authentication
Search engines
Cloud services
Hosting APIs (see later slides)

19
Q

Uses of server side processing elsewhere

A

Traditional file storage (e.g. a NAS)
Infrastructure (for LANs and WANs)
Virtual machines for thin clients

20
Q

Advantages of server side processing

A

Can access secure data and control what the client sees.
Should be far more secure against code manipulation.
The server is probably more powerful than the client so can potentially tackle heavy workloads in less time.

21
Q

Uses of Client side on web side?

A

Interactivity without page reloads
Validation rules
Animations, games, etc.
Responsive design
Any ‘offline’ abilities

22
Q
A