Browse Source

enriched readme, roadmap, added documents to explain web browsers and servers

master
apoc 6 months ago
parent
commit
545758f7d5
4 changed files with 58 additions and 13 deletions
  1. 16
    0
      README.md
  2. 3
    2
      docs/Roadmap.md
  3. 29
    0
      docs/Series/4. http, servers/4.2 Web servers and browsers.md
  4. 10
    11
      docs/issue-tracker.org

+ 16
- 0
README.md View File

@@ -1,2 +1,18 @@
# bazaar-design
web design for the bazaar application

# roadmap
in docs/roadmap.md

# issue tracker
in docs/issue-tracker.org

# daily "how-it-works" documents
in docs/Series/

You don't have to go through all of them, start from the latest addition and

if you don't understand something look at the one before it and
if you don't understand something look at the one before it and
if you don't understand something look at the one before it and
if you don't understand something look at the one before it.

+ 3
- 2
docs/Roadmap.md View File

@@ -16,9 +16,10 @@ Apr 2020 - Computing basics
Apr 2020 - CLI basics
May 2020 - Git basics
May 2020 - Introduction of ALGOL-like programming languages
??? 2020 - Filesystems
MAY 2020 - Filesystems
??? 2020 - CURRENT: web servers, browsers, & URIs (WWW)
??? 2020 - ...
??? 2020 - PHP & the filesystem, reading out data from a flat file
??? 2020 - WWW, HTML, HTTP, CGI
??? 2020 - Uniform Resource Locator(URI), handling navigation and resources
??? 2020 - PHP & the fs, writing data into a flat file
??? 2020 MILESTONE: Implementation of flat file storage

+ 29
- 0
docs/Series/4. http, servers/4.2 Web servers and browsers.md View File

@@ -0,0 +1,29 @@
Now that you've setup XAMPP it's time to see how it all ties together. Depending on your Operating System you should have the XAMPP control panel system-tray or shortcut someplace.

Once you start the XAMPP control panel you will be greeted with START|STOP|RESTART options for apache, mysql, filezilla, mercury, and tomcat.

We are for now only interested in apache. Now matter what runs by default, ensure that apache is started and is running.

It is, in a way, considered to go without saying that apache will take care of running PHP. These "obvious" (but not obvious at all) things occur seldom but unforunately they still occur.

If all's green you should be safe to open up a web browser and enter http://localhost in the address bar then press ENTER (navigate to localhost), and the default XAMPP splash-screen-page-thing should load.

So to combine all previous notes in these documents, let's summarize what happened:

1. you opened your browser by instructing your operating system to execute the browser binary program "mozilla firefox" (or "google chrome" (or "internet explorer" (you get the picture)))
2. the browser binary program has rendered its interface to your screen
3. you entered the "http://localhost" text string into the address bar and pressed ENTER
4. the browser binary program acknowledged the instruction and sent an HTTP request to the HTTP server located at http://localhost (our apache installation in this case)
5. the HTTP server picked up on this request while listening for HTTP requests, and resolved it to load the (default built-in) index.html file it comes packaged with
6. the HTTP server loads the content of the index.html file into its memory, then gives it to the browser as an HTTP response
7. The browser turns the HTTP response (in our case HTML) then based on the HTML structure, displays the index.html document within its interface

Now is the part when filesystems and pathnames come into play, see point #5, the HTTP server resolves a request to http://localhost as a request to respond with index.html. What is this index.html and where did XAMPP programmers put it?

Depending on your OS it will be either C:\xampp\htdoc\index.html, /var/www/html/index.html, or a path similar to these. It is a sample document and you can open and edit the text or content within, reload the page in your browser and the changes will be there.

Why?

Because on each reload the browser sends an HTTP request to the HTTP server which resolves to give the content of that index.html in an HTTP response.

Next up: URIs.

+ 10
- 11
docs/issue-tracker.org View File

@@ -11,17 +11,6 @@

None yet

*** DOING Docs: write up on filesystem
**** Issue

The filesystem is a tricky road with many twists and turns, write up information needed to read out one of the sample files with PHP.
Also write up on how PHP can talk to the file system.

**** Solution

./Series/3. filesystem/3.1 Usage.md
./Series/3. filesystem/3.2 Paths.md

*** TODO HTML#1.2.3 from Definitions.md
**** Issue

@@ -38,3 +27,13 @@
None yet.

** Closed
*** DONE DOING Docs: write up on filesystem
**** Issue

The filesystem is a tricky road with many twists and turns, write up information needed to read out one of the sample files with PHP.
Also write up on how PHP can talk to the file system.

**** Solution

./Series/3. filesystem/3.1 Usage.md
./Series/3. filesystem/3.2 Paths.md

Loading…
Cancel
Save