Skip to content

Instantly share code, notes, and snippets.

@mheap
Created April 13, 2015 20:14
Show Gist options
  • Save mheap/fdd581e9cbd26c8dae1f to your computer and use it in GitHub Desktop.
Save mheap/fdd581e9cbd26c8dae1f to your computer and use it in GitHub Desktop.
HTTP is your friend

We’ve all used HTTP before - we use it every time we go to Google or Facebook, every time we refresh our Twitter client on our phone.

HTTP is a very well defined protocol that we can use to build our own apps. It guarantees a response if you make a request, it has predefined error codes that everyone implements and it’s a very simple format to read if you need to inspect what’s going on by looking at it.

This talk takes you through HTTP, starting at the beginning with how a connection is established, parsed and how the response is formatted. We’ll also cover things like status codes, common headers and some advanced topics such as HTTP streaming and web sockets.

HTTP is at the core of almost everything we do as web developers, so having a strong understanding of it makes our life much easier when trying to work out what’s going on.

Understanding HTTP basics such as the request/response format and some more advanced topics such as HTTP streaming are fast becoming a necessity of jobs everywhere.

We’ll also take a look at tools such as HTTPBin and Charles and how they can be used to help debug any issues.

@benedmunds
Copy link

I would drop this whole paragraph

"HTTP is a very well defined protocol that we can use to build our own apps. It guarantees a response if you make a request, it has predefined error codes that everyone implements and it’s a very simple format to read if you need to inspect what’s going on by looking at it."

Actually I think I'd compress the two into something like this:

"Understanding HTTP basics such as the request/response format and some more advanced topics such as HTTP streaming are fast becoming a necessity of jobs everywhere.

This talk takes you through HTTP, starting at the beginning with how a connection is established, parsed and how the response is formatted. We’ll also cover things like status codes, common headers and some advanced topics such as HTTP streaming and web sockets."

This gives you a hook from the start, explains what you plan to cover, and keeps it succinct.

@ircmaxell
Copy link

Try making your abstract more front-heavy. It takes until the third paragraph to read what the talk is going to be about. You want to let them know what you're going to talk about in the first two sentences, and then build upon it.

I think the content that you have is pretty good, I just think you can rearrange it to be a bit more friendly to the reader.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment