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.
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.