So just be thoughtful before you suggest something too outlandish.

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

Okay, so we add the post function.

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

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

We don't want to use their IP. We want to use any IP. That's the URL we'll be requesting.

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

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

Lemon tree, very pretty.

Then we have another function for reading a secure cookie.

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

Nothing magical there.

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

I'll import the Web App module and then define a handler, which will handle the requests from the application.

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

Output tab.

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

I learned how to do this just by looking in the App Engine docs.

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

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

What the Google framework allows us to do is have a different function for each type of method request.

Now I can go back to my browser and see this is immediately working.

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

So we have you, and we have our servers, and you make a request for the form.

However, we didn't handle it in our parser, so we must handle it now.

Any requests?

Everything's as requested.

Networks are all about abstraction.

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

I didn't request you to do that.

Let's talk about how they're going to fit into things.

You can see the referer header referer header is interesting.

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

Returns the output of the command if successful otherwise returns FALSE.

We'll do so aha!

We treat them.

Let's go ahead and import that.

I'll try it myself okay we have our form, I click submit, and boom here we are.

Don't tell me who to do!

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

And then the time the message was left.

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.

I shall sing of your dastardly deed.

Handle the tasks, resources, and cost of your projects