On Github RCopeland / talk-how-the-internet-works
details here
Oh hey, these are some notes. They'll be hidden in your presentation, but you can see them if you open the speaker notes window (hit 's' on your keyboard).Let's talk about Client and Server
The Browsers
#1 - The Client hits a URL (by typing it, or hitting a link)
#2 - The Server receives the request, then performs any logic required to create the page.
#3 - The Server then delivers the page back down to the client.
#4 - The Client receives and then draws the page, so that the user can interact with it.
A contact form
Let's assume its by itself on a page, and its already been loaded by the Client.
If the user types something, we should check it for errors...
It's done first on the Client side.
When the form is filled out, and user free, we click the Send button.
Then the Client will send it up to the Server.
When the Server gets the data, we check it again.
Why? Because you can never trust anything from the user.
Finally, the Server will take the data and perform the necessary steps to complete the task.
In this case, it will send an email to the site owner with the message.
Let's talk about it now.
So, when the Client receives its response from the server, it gets:
Document Structure
Keywords:
Look and Feel
Keywords:
Actions that happen without a page refresh
Keywords:
http://www.github.com/RCopeland/talk-how-the-internet-works