Karteikarten
Server and Clients
Karten in diesem Stapel (19)
- 1Name 4 Server side rendering prosThe initial page of a website loads faster
It’s great for static sites
It’s rendering is great for SEO (search engine optimization)
The client can be very light weight - 2Name 5 Server side rendering cons If I were to create an app that needs the same data that a website
uses I would have to scrape the website to get the data
Frequent server requests
An overall slow page rendering
Full page reloads
Non-rich (non-dynamic) site interactions - 3Name 6 Client side rendering pros The server can just send DATA (e.g on JSON format)!
Each client can render the data differently
The programming language of the clients doesn´t matter
Rich site interactions (dynamic interactions)
Fast website rendering after the initial load
Great for web applications - 4Name 4 Client side rendering cons websites won’t be able to load until ALL the JavaScript is
downloaded to the browser
Search engines take a big hit
Initial load might require more time
In most cases, requires an external library - 5What is Status code 100Continue
- 6What is Status code 200Ok
- 7What is Status code 201Created
- 8What is Status code 204No content
- 9What is Status code 202Accepted
- 10What is Status code 300Multiple choices
- 11What is Status code 301Moved Permanently
- 12What is Status code 400Bad Request
- 13What is Status code 401Unauthorized
- 14What is Status code 402Payment required
- 15What is Status code 403Forbidden
- 16What is Status code 404Not found
- 17What is Status code 412Precondition failed
- 18What is Status code 500Internal server error
- 19What is Status code 503Service unavailable
Informationen
- Beschreibung
- Vefforritun Karteikarten am Server and Clients, erstellt von Kristin Sif Vigfusdottir am 13/11/2017.
- Erstellt von
- Kristin Sif Vigfusdottir
- Aufrufe
- 1
- Bewertung