How To Make Internet

Understanding how computers render webpages facilitates proper development. There are two general approaches, server side and client side. Both tactics rely on the same process for the first page request.

A device sends a request to a server, via the internet. A server assembles a file, and returns that file to the device via the internet. The device then renders the file as a webpage.

Server Side Vs. Client Side

Some websites use a database and a language like PHP to assemble the file sent. The server passes the request though a database to determine what resources to send. Each subsequent page must then be requested via the internet, the server and a subsequent pass through the database. This approach is a server side approach.

Other websites use a language like ember to store parts in the Dom. A request has passes through the server. A file is sent to the device, but first passes through the Dom. The Dom acts like a database on the client’s computer. Furue requests do not have to pass through the internet or the server again. Instead, all subsequent requests simply pass through the Dom to render the new page.

Why knowing this matters

Understanding web page assembly aids in de-bugging and page speed optimization. A server side approach relies on good internet speed, caching and compressing files to provide a fast experience. Client side tactics rely more heavily on the device for a snappy response time.

Neither approach is necessarily better, but rather must be weighed in conjunction with the desired results, and target audience.

Server Side Vs. Client Side