Skip to content

Instantly share code, notes, and snippets.

@simensen

simensen/gist:1c68679682cbae35a840 Secret

Last active August 29, 2015 14:15
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save simensen/1c68679682cbae35a840 to your computer and use it in GitHub Desktop.
Save simensen/1c68679682cbae35a840 to your computer and use it in GitHub Desktop.
Download ZIP
beau's notes for ep16
Raw
gistfile1.md

Podcast

Things in which I'm involved

Sculpin

Sculpin site

Found Projects

Looking forward to doing API work again soon. Designing proper data representations is much easier than proper UI-wrangling in my experience — @iansltx

Work

  • direct access to domain objects from API
    • no control
    • relying on framework events (syfony & doctrine)
  • phpunit-speedtrap by @johnkary via @bbene
  • phpunit-clever-and-smart
    1. Failures and errors
    2. So far unrecorded tests
    3. Remaining tests by execution time in ascendant order (fastest first)

Personal

  • Kingsman
    • blood & gore :(
    • felt like different director for second half of movie?
    • is samuel l jackson ever the good guy?
  • Captain America: The Winter Soldier
    • couldn't rent online?
    • same story as kingsman?!
    • also, samuel l jackson was in it too and he was a good guy
    • (and now i've remembered mace windu was a good guy)

HTTP/2.0

From the FAQ:

http://http2.github.io/faq/

What are the key differences to HTTP/1.x?

At a high level, HTTP/2:

  • is binary, instead of textual
  • is fully multiplexed, instead of ordered and blocking
  • can therefore use one connection for parallelism
  • uses header compression to reduce overhead
  • allows servers to “push” responses proactively into client caches

Can HTTP/2 make cookies (or other headers) better?

This effort was chartered to work on a revision of the wire protocol – i.e., how HTTP headers, methods, etc. are put “onto the wire”, not change HTTP’s semantics.

Nine Things to Expect from HTTP/2 by Mark Nottingham (@mnot)

I currently chair the IETF HTTP Working Group and am a member of the W3C TAG.

1. Same HTTP APIs

2. Cheaper Requests

Exploring Header Compression in HTTP/2.0

  • low hanging fruit

4. Cache Pushing

Innovating with HTTP 2.0 Server Push

Strange name.

5. Being Able to Change Your Mind

Again, this is about improving perceived performance and network friendliness; by allowing clients to keep the connection alive in this common scenario, extra roundtrips and resource consumption are avoided.

6. More Encryption

Firefox and Chrome have said that they’ll only support HTTP/2 using TLS.

They have two reasons for this. One is that deploying a new version of HTTP across the Internet is hard, because a lot of “middleboxes” like proxies and firewalls assume that HTTP/1 won’t ever change, and they can introduce interoperability and even security problems if they try to interpret a HTTP/2 connection.

The other is that the Web is an increasingly dangerous place, and using more encryption is one way to mitigate a number of threats. By using HTTP/2 as a carrot for sites to use TLS, they’re hoping that the overall security of the Web will improve.

https://letsencrypt.org/

My Takes

No More Text / binary / "Same HTTP APIs"

Many mentions about "middleboxes" and the problems they pose.

Summary

If I can leverage all this without changing how I think about HTTP 1.0/1.1 works, all the better. It seems like leveraging some of these features manually will be a lot of work.

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