beau's notes for ep16by simensen
- PHP Jeopardy at #phpbnl15
- Voicemail first PR! (by @dzuelke) David Zuelke
- Luke Stokes / Dave Ramsey / Brandon Meuller
- Sponsoring @coderabbi's Wisdom as a Service.
- Christopher Moss (@a6_chris) - really enjoyed #1 & #10
- Mark Railton @railto
Things in which I'm involved
- PSR-7 HTTP Message Interface under REVIEW!
- Wisdom of the ElePHPant (srcmvn post about it)
- devbookclub.org (clean code) (a sculpin site) - chapter 3 on tuedssay, march 3rd. @jcarouth
- Logo for Chris Tankersley by ninjagrl (vectorized by beau; essentially beau just clicked a button.)
- "stack" #ossart (oss.ninjagrl.com, stackphp)
- Sculpin's blog
- Using Travis to build your Sculpin blog by @wouterjnl
- reStructuredText for Sculpin by @rjkip
- Adam Brett @sixdaysad
- @stauffermatt (Matt Stauffer)
- @adamwathan (Adam Wathan)
- Rapid Application Development - From Idea to Prototype in 1:45 with Laravel
- http://gistlog.co/simensen/1c68679682cbae35a840 (so meta)
- @iansltx (Ian Littman)
- @codebyjeff (Jeff Madsen)
Looking forward to doing API work again soon. Designing proper data representations is much easier than proper UI-wrangling in my experience — @iansltx
- direct access to domain objects from API
- no control
- relying on framework events (syfony & doctrine)
- phpunit-speedtrap by @johnkary via @bbene
- Failures and errors
- So far unrecorded tests
- Remaining tests by execution time in ascendant order (fastest first)
- 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)
From the 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.
I currently chair the IETF HTTP Working Group and am a member of the W3C TAG.
1. Same HTTP APIs
2. Cheaper Requests
- low hanging fruit
4. Cache Pushing
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.
No More Text / binary / "Same HTTP APIs"
Many mentions about "middleboxes" and the problems they pose.
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.