WebRTC HTTP/2 all the things! challenges, opportunities, and the exciting world ahead of us... +Ilya Grigorik @igrigorik
HTTPbis Working Group Y. Hirano Internet-Draft Google, Inc. Intended status: Standards Track February 14, 2014 Expires: August 18, 2014 WebSocket over HTTP/2.0 draft-hirano-httpbis-websocket-over-http2-00 Abstract The WebSocket protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that co
è¿½è¨ @jovi0608 ããã«é常ã«ä¸å¯§ã«ã³ã¡ã³ããããã ãã¾ããã https://gist.github.com/shigeki/ba7941d114344ddd4b01 æ¬æ CROSS 2014ã®æ¬¡ä¸ä»£Webã»ãã·ã§ã³ã«åå ããã ããããåºæ¿ãåããã®ã§ãç¹ã«ãWebã¢ããªã±ã¼ã·ã§ã³ãéçºã»éç¨ããä¸ã§ãä»å¾ã©ãå½±é¿ãã¦ããã ããã¿ãããªè¦ç¹ã§æ´çãããã¨ãæ¸ãã¦ã¿ãã 次ä¸ä»£Webã»ãã·ã§ã³ã¯å»å¹´ãUSTã§è¦ã¦ã¦ããã£ã¡ãé¢ç½ãã£ãã®ã§ãä»å¹´ã¯çã§èãã«æ¥ãã å»å¹´ã®ã»ãã·ã§ã³ã®è°è«ã¯ã naoyaããã®è¨äºãé°å²æ°ãããããããã£ãã Webã¯ã¤ã³ã¿ã¼ãããã«ãªã£ã - naoyaã®ã¯ã¦ãªãã¤ã¢ãªã¼ å»å¹´ãSPDYã®å 容ã¨ã追ã£ã¦ã¦ãHTTP/1.1ã¨ä½ãéãã®ãã¿ãããªãã¨ã調ã¹ã¦æ¸ããããã¦ãã SPDYã§è¤æ°ã®TCPã³ãã¯ã·ã§ã³ãã²ã¨ã¤ã«ã¾ã¨ããã¨ã¯ã©ããããã¨ã -
https://insouciant.org/tech/http-slash-2-considerations-and-tradeoffs/1 comment | 0 pointsChromiumã®éçºãã¼ã ã®William ChangããHTTP/2ã®è¦æ¤è¨äºé ã¨ãã®ãã¬ã¼ããªãã«ã¤ãã¦ã¾ã¨ãã¦ãã¾ããHTTP/2.0ã¨SPDYã®æ¦è¦ã«ã¤ãã¦ã¯ãAkamaiã®ãã®10åã®ãããªãåç §ãã ããã 1) Network Performance HTTP/1.xã¯ããããã¯ã¼ã¯ã®å©ç¨ãéå¹çãHTTP Pipeliningï¼ããã¯ããã§åºæã®åé¡ããããï¼ãé¤ãã¦ãHTTP/1.xã¯ãæ¥ç¶ãããä¸ã¤ã®ãã©ã³ã¶ã¯ã·ã§ã³ããã§ããªããã¨ããHOL (Head of line) blockingã®åå ã¨ãªããHOL blockingã¯ã©ã¦ã³ãããªããã®ã³ã¹ããé«ãããã¼ã¸èªè¾¼ã¿ã®ããã©ã¼ãã³ã¹ãæªå
ãã®ææ¸ã¯ãHypertext Transfer Protocol version 2.0 (draft-ietf-httpbis-http2-06)ãã®æ¥æ¬èªè¨³ã§ãã åæã®ææ°ç ã¯ããã®æ¥æ¬èªè¨³ãåç §ããçããæ´æ°ããã¦ããå¯è½æ§ãããã¾ãã åæã¯ãã©ããçã§ãããHTTP 2.0 ã¯ç¾å¨çå®ä¸ã®ä»æ§ã§ãããã¨ã«åå注æãã¦ãã ããã ãã®æ¥æ¬èªè¨³ã¯åèæ å ±ã§ãããæ£å¼ãªææ¸ã§ã¯ãªããã¨ã«ã注æãã¦ãã ãããã¾ãã翻訳ã«ããã¦çãã誤ããå«ã¾ããå¯è½æ§ããããããå¿ ãåæããããã¦åç §ãããã¨ãæ¨å¥¨ãã¾ãã å ¬éæ¥: 2013-08-26 æ´æ°æ¥: 2013-09-23 翻訳è : Moto Ishizawa <[email protected]> 翻訳åå: Shigeki Ohtsu æ¦è¦ ãã®ä»æ§æ¸ã¯ãæé©åããã Hypertext Transfer Protocol (HT
ãã®ææ¸ã¯ãHypertext Transfer Protocol version 2.0 (draft-ietf-httpbis-http2-04)ãã®æ¥æ¬èªè¨³ã§ãã åæã®ææ°ç ã¯ããã®æ¥æ¬èªè¨³ãåç §ããçããæ´æ°ããã¦ããå¯è½æ§ãããã¾ãã åæã¯ãã©ããçã§ãããHTTP 2.0 ã¯ç¾å¨çå®ä¸ã®ä»æ§ã§ãããã¨ã«åå注æãã¦ãã ããã ãã®æ¥æ¬èªè¨³ã¯åèæ å ±ã§ãããæ£å¼ãªææ¸ã§ã¯ãªããã¨ã«ã注æãã¦ãã ãããã¾ãã翻訳ã«ããã¦çãã誤ããå«ã¾ããå¯è½æ§ããããããå¿ ãåæããããã¦åç §ãããã¨ãæ¨å¥¨ãã¾ãã å ¬éæ¥: 2013-08-20 æ´æ°æ¥: 2013-09-01 翻訳è : Moto Ishizawa <[email protected]> æ¦è¦ ãã®ä»æ§æ¸ã¯ Hypertext Transfer Protocol (HTTP) ã·ã³ã¿ãã¯ã¹ã®æé©åããã表ç¾ã«ã¤ãã¦è¿°ã¹ã¾ã
By Ilya Grigorik on June 12, 2013 HTTP 2.0 enables the server to send multiple responses (in parallel) for a single client request - aka, server push. Except, why would we ever want to do such a thing? Well, an average page requires dozens of additional assets, such as JavaScript, CSS, and images, and references to all of these assets are embedded in the very HTML that the server is producing! Hen
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}