Everything's as requested.

We can talk about users and how much trouble they cause us.

So first we'll go to our Editor and we'll switch these lines around again so we can see the actual request.

Well I'll take what I can get.

And so the industry standard is don't cache POST requests.

Is it after the HTTP request headers?

Okay quick quiz

Any requests?

Did you see garbage?

One is too much load, as in a database that's just doing too much work.

Come on down. For, uh, encores I do requests, so I'm afraid you're just gonna have to wing it.

If somebody requested Chopsticks you'd ask for the sheet music.

Don't tell me who to do!

This is where XMLHttPRequest come in.

We could have our servers in this case we'll use the Hipmunk example.

GET parameters are included in the URL and POST parameters are included in the body.

the IPP request failed for an unknown reason

Next, we specify the onload parameter, which is a function that we define that gets called once the server responds to our request.

The IPP request failed for an unknown reason.

Their servers are probably on fire, because it's Twitter.

In our cases, we're pretty much always going to want to use GET. Second, we specify the URL to call out to.

POST requests, on the other hand, are okay to change the Server.

That's kind of a side effect of the fact that we're not printing the actual request.

This is a piece of music he specially requested. Start the tape, please Holly.

And now we can go back and view this in our browser.

Another difference is that GET parameters are generally okay to cache.

Output tab.

But since Mr. Meegar has been enhanced he'll give off a stronger signal than your average Joe.

Networks are all about abstraction.

But do you remember from our first lesson when we talked about

And then the time the message was left.

You don't strictly need this.

We'll be talking about it in Unit 6,

It was not.

We'll call this get_cords, and this is the first function we're going to be implementing.

The methods of this class will handle HTP requests.

If you don't specify method at all, it defaults to get, and that's what we've been seeing.

I can't remember a night when I didn't get at least 3 requests for it.

So remember I drew this picture before of you and the servers making requests, or you and your browser.

Fetching a document, updating data, requests that can be cached or sending a lot of data to the server?

This will save us from having to call get_page twice. Get_page is fairly expensive.

Alright, now let's try creating our own XML HTTP request.

This list doesn't mean anything. They're just requests.

So just be thoughtful before you suggest something too outlandish.

When we handle unit2 welcome, we come to this handler here, welcome.