Preskoči na sadržaj
Korištenjem servisa na Twitteru pristajete na korištenje kolačića. Twitter i partneri rade globalno te koriste kolačiće za analize, personalizaciju i oglase.

Za najbolje sučelje na Twitteru koristite Microsoft Edge ili instalirajte aplikaciju Twitter iz trgovine Microsoft Store.

  • Naslovnica Naslovnica Naslovnica, trenutna stranica.
  • O Twitteru

Spremljena pretraživanja

  • obriši
  • U ovom razgovoru
    Ovjeren akauntZaštićeni tweetovi @
Predloženi korisnici
  • Ovjeren akauntZaštićeni tweetovi @
  • Ovjeren akauntZaštićeni tweetovi @
  • Jezik: Hrvatski
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English
    • English UK
    • Español
    • Filipino
    • Français
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Български език
    • Русский
    • Српски
    • Українська мова
    • Ελληνικά
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Imate račun? Prijava
    Imate račun?
    · Zaboravili ste lozinku?

    Novi ste na Twitteru?
    Registrirajte se
Profil korisnika/ce jgbarah
Jesus M Gonzalez-Barahona
Jesus M Gonzalez-Barahona
Jesus M Gonzalez-Barahona
@jgbarah

Tweets

Jesus M Gonzalez-Barahona

@jgbarah

I'm me, my circumstances, and my Internet connection. También tuiteo en español como @jgbarah2

gsyc.es/~jgb
Vrijeme pridruživanja: kolovoz 2009.

Tweets

  • © 2020 Twitter
  • O Twitteru
  • Centar za pomoć
  • Uvjeti
  • Pravila o privatnosti
  • Imprint
  • Kolačići
  • Informacije o oglasima
Odbaci
Prethodni
Sljedeće

Idite na profil osobe

Spremljena pretraživanja

  • obriši
  • U ovom razgovoru
    Ovjeren akauntZaštićeni tweetovi @
Predloženi korisnici
  • Ovjeren akauntZaštićeni tweetovi @
  • Ovjeren akauntZaštićeni tweetovi @

Odjava

Blokiraj

  • Objavi Tweet s lokacijom

    U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više

    Vaši popisi

    Izradi novi popis


    Manje od 100 znakova, neobavezno

    Privatnost

    Kopiraj vezu u tweet

    Ugradi ovaj Tweet

    Embed this Video

    Dodajte ovaj Tweet na svoje web-mjesto kopiranjem koda u nastavku. Saznajte više

    Dodajte ovaj videozapis na svoje web-mjesto kopiranjem koda u nastavku. Saznajte više

    Hm, došlo je do problema prilikom povezivanja s poslužiteljem.

    Integracijom Twitterova sadržaja u svoje web-mjesto ili aplikaciju prihvaćate Twitterov Ugovor za programere i Pravila za programere.

    Pregled

    Razlog prikaza oglasa

    Prijavi se na Twitter

    · Zaboravili ste lozinku?
    Nemate račun? Registrirajte se »

    Prijavite se na Twitter

    Niste na Twitteru? Registrirajte se, uključite se u stvari koje vas zanimaju, i dobivajte promjene čim se dogode.

    Registrirajte se
    Imate račun? Prijava »

    Dvosmjerni (slanje i primanje) kratki kodovi:

    Država Kod Samo za korisnike
    Sjedinjene Američke Države 40404 (bilo koje)
    Kanada 21212 (bilo koje)
    Ujedinjeno Kraljevstvo 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Irska 51210 Vodafone, O2
    Indija 53000 Bharti Airtel, Videocon, Reliance
    Indonezija 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italija 4880804 Wind
    3424486444 Vodafone
    » Pogledajte SMS kratke šifre za druge zemlje

    Potvrda

     

    Dobro došli kući!

    Vremenska crta mjesto je na kojem ćete provesti najviše vremena i bez odgode dobivati novosti o svemu što vam je važno.

    Tweetovi vam ne valjaju?

    Prijeđite pokazivačem preko slike profila pa kliknite gumb Pratim da biste prestali pratiti neki račun.

    Kažite mnogo uz malo riječi

    Kada vidite Tweet koji volite, dodirnite srce – to osobi koja ga je napisala daje do znanja da vam se sviđa.

    Proširite glas

    Najbolji je način da podijelite nečiji Tweet s osobama koje vas prate prosljeđivanje. Dodirnite ikonu da biste smjesta poslali.

    Pridruži se razgovoru

    Pomoću odgovora dodajte sve što mislite o nekom tweetu. Pronađite temu koja vam je važna i uključite se.

    Saznajte najnovije vijesti

    Bez odgode pogledajte o čemu ljudi razgovaraju.

    Pratite više onoga što vam se sviđa

    Pratite više računa da biste dobivali novosti o temama do kojih vam je stalo.

    Saznajte što se događa

    Bez odgode pogledajte najnovije razgovore o bilo kojoj temi.

    Ne propustite nijedan aktualni događaj

    Bez odgode pratite kako se razvijaju događaji koje pratite.

    Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
    • Prijavi Tweet

    HTTP/3 is being deployed in production for all of us, and that could be important for you and me and the Internet. (Short) thread ahead

    00:09 - 27. ruj 2019.
    • 1.396 proslijeđenih tweetova
    • 2.650 oznaka „sviđa mi se”
    • Iqbal Ansari Njeri me0w Subhash Dasyam mauro_iker Matyo Reynaldo Cordero 💚💙 New Story Studio codeBender
    17 replies 1.396 proslijeđenih tweetova 2.650 korisnika označava da im se sviđa
      1. Novi razgovor
      2. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        HTTP is this protocol that makes the web work https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol … It was first described (and implemented) in 1989 (you know: @timberners_lee and his team and the @CERN and all that), but it was first formally specified as HTTP/0.9 in 1991.

        1 reply 1 proslijeđeni tweet 56 korisnika označava da im se sviđa
        Prikaži ovu nit
      3. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        HTTP/0.9 was a simple protocol built on top of TCP, using plain text headers, with no encryption, very limited in functionality, but doing its task well enough for those ages. Its description is like one page long: https://www.w3.org/Protocols/HTTP/AsImplemented.html …

        1 reply 1 proslijeđeni tweet 57 korisnika označava da im se sviđa
        Prikaži ovu nit
      4. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        HTTP was a great success, with Mosaic http://www.ncsa.illinois.edu/enabling/mosaic  and then https://en.wikipedia.org/wiki/Netscape  and then Explorer https://en.wikipedia.org/wiki/Internet_Explorer … in 1995. And millions of websites, and e-commerce, etc. etc. etc.

        1 reply 2 proslijeđena tweeta 44 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      5. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        People started to add some non-standard functionality both client-side and server-side (main servers at that time were NCSA HTTPd, later Apache; Netscape server; Microsoft IIS), and HTTP 1.0 was produced in 1996 (RFC1945) https://tools.ietf.org/html/rfc1945 

        1 reply 3 proslijeđena tweeta 43 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      6. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        But meanwhile, people were already working on HTTP 1.1, so that many of its features were already supported by clients and servers already in 1996. It was formally approved in 1997 as RFC2068, updated in 1999 as RFC2616 https://tools.ietf.org/html/rfc2616  (~170 pages long)

        1 reply 1 proslijeđeni tweet 42 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      7. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        HTTP 1.1 was the protocol that made it possible the big bang of the web, during the late 1990s and early 2000s. Still on TCP, still plain-text headers. But it could be used with encryption, single TCP connection of several interactions, and supported a lot of mechanisms.

        1 reply 1 proslijeđeni tweet 51 korisnik označava da mu se sviđa
        Prikaži ovu nit
      8. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        HTTP 1.1 was so successful (and the interests on HTTP were so varied and powerful), that until 2014 we didn't have an update... that was still HTTP 1.1 (six RFCs, usually named 723x, plus some complements) https://www.w3.org/Protocols/ 

        1 reply 1 proslijeđeni tweet 46 korisnika označava da im se sviđa
        Prikaži ovu nit
      9. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        This renovation of HTTP 1.1 had into account industry practices & demands, and tried to put some order in a period when the web was the dominant application in the Internet, and it needed to live up to that standard. But it was obvious a more drastic reform was needed.

        1 reply 1 proslijeđeni tweet 36 korisnika označava da im se sviđa
        Prikaži ovu nit
      10. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        Since 2009, Google, with the support of other important actors, had been working on SPDY. It changed HTTP in some significant ways: it was binary (forget plain text headers), it supported multiplexing of TCP connetions, header compression... https://www.chromium.org/spdy/spdy-whitepaper …

        1 reply 1 proslijeđeni tweet 50 korisnika označava da im se sviđa
        Prikaži ovu nit
      11. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        By 2012, Chrome, Firefox, and Opera supported SPDY, and some large web sites too (eg Facebook, Google, Twitter). It was in its path to become a de-facto standard. It's main advantage: it reduced latency *a lot*https://developers.google.com/web/fundamentals/performance/http2/ …

        1 proslijeđeni tweet 47 korisnika označava da im se sviđa
        Prikaži ovu nit
      12. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        But instead of letting SPDY become de-facto standard, after an open call it was used as the basis for HTTP 2, the new, shinny version of the protocol, released in 2015 as RFC 7540 (HTTP/2) and RFC 7541 (HPACK)

        1 reply 2 proslijeđena tweeta 46 korisnika označava da im se sviđa
        Prikaži ovu nit
      13. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        After this release of the new HTTP 2 "protocols", Google stopped SPDY, and waters came back to the "official standards" river https://developers.google.com/web/fundamentals/performance/http2/ … https://blog.chromium.org/2015/02/hello-http2-goodbye-spdy.html …pic.twitter.com/Q2RkV2TGt7

        1 reply 1 proslijeđeni tweet 53 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      14. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        HPACK, btw, is a very interesting addition to HTTP 2 https://blog.cloudflare.com/hpack-the-silent-killer-feature-of-http-2/ … It does Huffman encoding of headers, significantly reducing size (specially for requests with a small payload), and is more resilent to attacks aimed to sniff cookies

        1 reply 5 proslijeđenih tweetova 70 korisnika označava da im se sviđa
        Prikaži ovu nit
      15. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        HTTP 2 has been very successful in adoption, although few users may have noticed (except for better web performance for them). Main reasons are probably the multiplexing of HTTP requests on single TCP connections, and the header compressionpic.twitter.com/d2OrpgbYd2

        3 proslijeđena tweeta 52 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      16. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        But HTTP 2 was not radical enough. In a path that by now may be familiar, Google started to work on a more complete redesign of HTTP: the QUIC protocol https://www.chromium.org/quic 

        1 reply 2 proslijeđena tweeta 55 korisnika označava da im se sviđa
        Prikaži ovu nit
      17. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        QUIC is radical in several ways, but probably the most noticeable is its use of UDP as transport layer, instead of TCP. This means that QUIC had to implement reliability and order, as TCP does. And TLS. But it does it in its own way https://www.chromium.org/quic pic.twitter.com/wR0amzeUZp

        4 proslijeđena tweeta 82 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      18. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        As it happened with SPDY and HTTP 2, QUIC became the core of HTTP 3 https://http3.net/  https://www.zdnet.com/article/http-over-quic-to-be-renamed-http3/ …pic.twitter.com/PHEo276mlm

        1 reply 3 proslijeđena tweeta 53 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      19. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        Currently, HTTP 3 is still in the works https://quicwg.org/base-drafts/draft-ietf-quic-http.html … But is is expected to be stable until it is fully standardized, and it is already supported by some browsers, with others announced (Chrome, curl, soon Firefox)

        1 reply 5 proslijeđenih tweetova 49 korisnika označava da im se sviđa
        Prikaži ovu nit
      20. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        Today, Cloudflare has announced they are supporting HTTP 3 in their servers https://blog.cloudflare.com/http3-the-past-present-and-future/ … Since Cloudflare is running more than 10% of all the web servers in the world https://w3techs.com/technologies/details/cn-cloudflare/all/all … this is big news for HTTP 3 and QUICpic.twitter.com/J5Luf99kdU

        1 reply 30 proslijeđenih tweetova 122 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      21. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        And it also means a change in how Internet works, and likely a change in how we should teach Inet protocols from now on. Reliability, order & encryption for the web are now in QUIC, no longer in TCP and TLS.pic.twitter.com/atVGDO4EMY

        46 proslijeđenih tweetova 153 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      22. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        If you want to learn more about the details of QUIC and HTTP 3, have a look at "HTTP/3 Explained" https://http3-explained.haxx.se/en/  Some other references summarizing QUIC & HTTP 3: https://arstechnica.com/gadgets/2018/11/the-next-version-of-http-wont-be-using-tcp/ … https://medium.com/drill/the-internet-changes-http-3-will-not-use-tcp-anymore-427e82eeadc0 …https://kinsta.com/blog/http3/ 

        1 reply 81 proslijeđeni tweet 316 korisnika označava da im se sviđa
        Prikaži ovu nit
      23. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        BTW: Quiche, the implementation that Cloudflare is using for QUIC and HTTP 3, is based on @rustlang and is #freesoftwarehttps://github.com/cloudflare/quiche …

        1 reply 29 proslijeđenih tweetova 214 korisnika označava da im se sviđa
        Prikaži ovu nit
      24. Jesus M Gonzalez-Barahona‏ @jgbarah 27. ruj 2019.
        • Prijavi Tweet

        Final note: if after all this thread it happens that you don't know about how HTTP works, have a look at a very good summary in MDN https://developer.mozilla.org/en-US/docs/Web/HTTP/Overview … It is about HTTP 1.1, but most of it remains similar in HTTP 2 and HTTP 3 (except for how connections work, of course)

        8 replies 11 proslijeđenih tweetova 176 korisnika označava da im se sviđa
        Prikaži ovu nit
      25. Kraj razgovora

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

      Sponzorirani tweet

      false

      • © 2020 Twitter
      • O Twitteru
      • Centar za pomoć
      • Uvjeti
      • Pravila o privatnosti
      • Imprint
      • Kolačići
      • Informacije o oglasima