Server

Question 1

Server

Answer 1

Is a generic term referring to either software or hardware that processes request from clients. A server offers shared resources that can be requested for use by a client.

Question 2

Client

Answer 2

Is software that sends a request to a server to access a shared resource and processes the response returned from the server.

Question 3

http://www.techelevator.com:80/events/current?month=march&day=27#00h02m30s

Answer 3

http:// Protocol
www.techelevator.com Domain
:80 Port
/events/current Path to resource
? Query
month=march&day=27 Parameters
#00h02m30s Anchor/Fragment

Question 4

Domain names

Answer 4

Are composed of parts, each separated by a period. Domains start a top-level domain and then form a hierarchy of subdomains, each a child of the higher-level domain.

Question 5

dashboard.techelevator.com

Answer 5

.com is the top-level domain
.techelevator is a subdomain of .com
dashboard. is a subdomain of .techelevator.

Question 6

IP (Internet Protocol) Address

Answer 6

Identifies a computer or device on a network (including the internet). All devices/computers on a network must have an IP address to communicate with other devices/computers on the network. It gives the location of the device like the street address of a house.

Question 7

Types of IP Address

Answer 7

IPv4 - dotted-decimal notation

IPv6 - in hexadecimal

Question 8

DNS (Domain Name System)

Answer 8

Allows for easy-to-remember names for IP address. Like a map with string keys (techelevator.com) and IP address values (198.49.23.144)

Question 9

Port

Answer 9

Used to identify which server application should handle the request.
        Port 80 - HTTP
	Port 443 - HTTPS
	Port 25 - SMTP (Email Mail)
	Port 21 - FTP (File Transfer)
	Port 22 - SSH (Secure remote terminal)

Question 10

HTTP (HyperText Transfer Protocol)

Answer 10

It is a defined language and process they will use when the client makes a request and the server returns a response.

Question 11

Parts of an HTTP Request

Answer 11

1. Method.
2. Requested Resource.
3. Header.
4. Parameters.

Question 12

Parts of an HTTP Response

Answer 12

1. Status Code.
2. Header.
3. Content-Type.
4. Content (Body).

Question 13

Method (VERB) parts of an HTTP Request

Answer 13

GET - Retrieves information
POST - Adds information
PUT - Updates information
DELETE - Deletes information

Question 14

Method (VERB) part of an HTTP Request

Answer 14

GET - Retrieves information
POST - Adds information
PUT - Updates information
DELETE - Deletes information

Question 15

Requested Resource part of an HTTP Request

Answer 15

A resource is something shared by the client. It can be an HTML page, CSS, a file like an image or pdf document, information from a database, access to a stream, or anything else the server can deliver.

Question 16

Header part of an HTTP Request

Answer 16

The header contains details about the request, such as the browser, IP address, preferred language, etc.

Question 17

Parameters part of an HTTP Request

Answer 17

Parameters include data to be used to fulfill the request. Similar to arguments sent to a Java method.

Question 18

Status Code part of an HTTP Response

Answer 18

1xx - Informational
2xx - Success: 200 - OK, 201 - Created
3xx - Redirected: 301 - Moved Permanently
4xx - Client Error: 400 - Bad Request, 401 - Unauthorized, 403 - Forbidden, 404 - Resource Not Found
5xx - Server Error: 500 - Server Exception

Question 19

Header part of an HTTP Response

Answer 19

Meta Information about the response.

Question 20

Content-Type

Answer 20

The type of content being returned: text, JSON, image, stream, etc.

Question 21

Content (Body)

Answer 21

The output of the response. HTML, image, data, etc.

Question 22

API Application Programming Interface

Answer 22

Is a way for software components to talk to each other. The methods and properties in our classes that are exposed as the public are the API of the object.

Question 23

Web Service (Web API)

Answer 23

A Web Service or Web API is an API that allows for applications to communicate with each other across the internet. All Web Services are APIs, however, not all APIs are Web Services.

Question 24

REST (REpresentational State Transfer)

Answer 24

Is a software architectural pattern that defines a set of constraints and standards for how 2 applications on a network should communicate.

Question 25

Rules of REST:

Answer 25

1. Uniform Interface (URI, URL).
2. Stateless.
3. Cacheable.
4. Client-Server.
5. Layered System.

Question 26

REST Uniform Interface (URI, URL)

Answer 26

The uniform interface constraint defines the interface between clients and servers. It simplifies and decouples the architecture, which enables each part to evolve independently.

Question 27

REST Stateless

Answer 27

The necessary state to handle the request is contained within the request itself

Question 28

REST Cacheable

Answer 28

As on the World Wide Web, clients can cache responses.

Question 29

REST Client-Server

Answer 29

Clients are not concerned with data storage, which remains internal to each server so that the portability of client code is improved. Servers are not concerned with the user interface or user state so that servers can be simpler and more scalable.

Question 30

REST Layered System

Answer 30

Layers may also enforce security policies.

Question 31

REST Web Service (Web API)

Answer 31

Web Services that implement the REST standard are said to be RESTful. Commonly use JSON as a response.

Question 32

JSON (JavaScript Object Notation)

Answer 32

Is a messaging format that is commonly used by RESTful Web Services.
Uses key/value pairs to represent objects.
Objects are identified by { }, Arrays by [ ]
Objects have properties and values separated by a colon. The property names are Strings in double-quotes. The value can be a number, String (with double quotes), Array, or Object.
Each property/value pair, object, or array is separated by a comma.