Matt Klein

@mattklein123

Engineer . creator. CNCF TOC. Husband of & dad.

Seattle
Vrijeme pridruživanja: lipanj 2011.

Tweetovi

Blokirali ste korisnika/cu @mattklein123

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @mattklein123

  1. Prikvačeni tweet
    16. lip 2017.

    I'm not a normal blogger, but I wrote about a big decision that I have made over the last couple of months:

    Poništi
  2. 2. velj

    I'm doing a particularly ugly refactor, and it's during these moments that I most wonder how folks build anything other than small programs using dynamic languages; I would be utterly lost without static types and the compiler.

    Poništi
  3. 30. sij

    If people spent as much time doing actual engineering as they spent complaining about open source licenses/foundations/etc., computers would work a lot better.

    Poništi
  4. 30. sij

    50/50 chance there is a meeting somewhere at the Googleplex today titled: "throw darts at a picture of Matt Klein's head." 🎯

    Prikaži ovu nit
    Poništi
  5. 30. sij

    Just looked at the EU schedule and the program chairs selected very few Istio and Knative related talks. Not joining the foundation? No more free ride it seems!

    Prikaži ovu nit
    Poništi
  6. 30. sij

    Shipping software that is very widely used is a fascinating exercise in trying to improve the status quo while engaging in pragmatic compromise. At least no one has asked for HTTP/0.9 support. 😉

    Prikaži ovu nit
    Poništi
  7. 30. sij

    Note that we do not preserve the original header case that was received; headers are still normalized to lowercase internally. Preserving case would have been a large and disruptive change. Changing case during encoding was a pragmatic compromise to fix a real world issue.

    Prikaži ovu nit
    Poništi
  8. 30. sij

    However, many legacy apps have never properly handled header case insensitivity correctly, and Envoy's normalizing behavior breaks them. Not very long ago we added the ability for Envoy to re-CamelCase headers when encoding HTTP/1.1 to "fix" these apps.

    Prikaži ovu nit
    Poništi
  9. 30. sij

    This is not the only compromise that has been made in this area. The HTTP spec says that headers are case insensitive. HTTP/2 in fact requires lowercase headers, and by default Envoy normalizes all headers to lowercase since internally all HTTP traffic is normalized to HTTP/2.

    Prikaži ovu nit
    Poništi
  10. 30. sij

    Envoy is now used in more places than I ever would have imagined, and one of those places is bringing observability, security, etc. to legacy apps. As such, it no longer seemed reasonable to block support when the use cases are legitimate.

    Prikaži ovu nit
    Poništi
  11. 30. sij

    Some folks have asked why I did not block HTTP/1.0 support: I tried for a while, but the reality is that legacy apps run in prod that haven't been modified in years. Apps run that have no one familiar with how they work. Apps run that have lost source code!

    Prikaži ovu nit
    Poništi
  12. 29. sij

    HTTP/1.1 was ratified 23 years ago. When I started writing ~5 years ago I decided to not support HTTP/1.0. Not only did that not hold, but we continue to get HTTP/1.0 bugs filed against our support for it. Legacy really, truly is forever.

    Prikaži ovu nit
    Poništi
  13. proslijedio/la je Tweet
    28. sij

    The Power of Open Source ♥️: Todd Greer from Google is working on Envoy Proxy HTTP cache filter. It's still WIP, but from Hazelcast is already validating the API by implementing Hazelcast-based filter. It Feels Good to be an Early Adapter!

    Poništi
  14. 28. sij

    Chaser. Working with the community on has been the most gratifying experience of my career by far, but it still surprises and saddens me when folks show up with this level of entitlement. I am NOT a vendor!

    Prikaži ovu nit
    Poništi
  15. 28. sij
    Prikaži ovu nit
    Poništi
  16. 27. sij

    OH: "It's like the CAP theorem says we can have 2/3 and gives us 1.5/3." Me: Web scale costs 0.5.

    Poništi
  17. proslijedio/la je Tweet
    21. sij

    Just published a post on how Lyft's mobile networking infrastructure has changed and evolved as our team grew to >150 mobile engineers:

    Poništi
  18. 20. sij

    As we have joked many times, is mostly an API that occasionally forwards some packets around. 😀 Please poke to write a blog post on the tech behind this release because it's pretty amazing!

    Prikaži ovu nit
    Poništi
  19. 20. sij

    Note: this release begins the 1 year deprecation cycle of our v2 API and introduces the v3 API. Please see the linked documentation in the email. did some magical tooling work in this release that will allows us to scalably support multiple API versions simultaneously.

    Prikaži ovu nit
    Poništi
  20. 20. sij

    Announcing v1.13.0! Huge thanks to our amazing maintainers, contributors, and community. I ♥️ what we are all accomplishing together. 📈🚀

    Prikaži ovu nit
    Poništi
  21. 16. sij

    I just half jokingly told someone to ask for an advance on their promotion salary bump in order to pay for the stars that will be used to justify their promotion. 🤔⭐️💰

    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·