[B! HTTP2] Itisangoã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯

Itisango id:Itisango

HTTP2ã«é–¢ã™ã‚‹Itisangoã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯ (12)

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

${{author_name}}$
{{author_name}}{{created}}
{{ #comment }}{{ comment }}{{ /comment }}
- {{ label }}

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

Pub/Subãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ãƒ³ã‚°ãƒ¢ãƒ‡ãƒ«
Pub/Subãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ãƒ³ã‚°ãƒ¢ãƒ‡ãƒ«ã¯ï¼Œãƒ‘ãƒ–ãƒªãƒƒã‚·ãƒ¥ãƒ»ã‚µãƒ–ã‚¹ã‚¯ãƒ©ã‚¤ãƒ–ï¼ˆPublish-Subscribeï¼‰æ–¹å¼ã§ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã‚’é€å—ä¿¡ã™ã‚‹ãŸã‚ã®ãƒ¢ãƒ‡ãƒ«ã§ã™ã€‚ ï¼œã“ã®é …ã®æ§‹æˆï¼ž (1)ã€€Pub/Subãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ãƒ³ã‚°ãƒ¢ãƒ‡ãƒ«ã«ã‚ˆã‚‹ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã®é€å—ä¿¡ (2)ã€€Pub/Subãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ãƒ³ã‚°ãƒ¢ãƒ‡ãƒ«ã®ç‰¹å¾´ (3)ã€€æ°¸ç¶šåŒ–ã‚µãƒ–ã‚¹ã‚¯ãƒ©ã‚¤ãƒãƒ¼ã®åˆ©ç”¨ Pub/Subãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ãƒ³ã‚°ãƒ¢ãƒ‡ãƒ«ã§ã¯ï¼Œãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã‚’ä½œæˆã—ã¦é€ä¿¡ã™ã‚‹é€ä¿¡å´ã®ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆï¼ˆãƒ—ãƒãƒ‡ãƒ¥ãƒ¼ã‚µãƒ¼ï¼‰ã‚’ãƒ‘ãƒ–ãƒªãƒƒã‚·ãƒ£ãƒ¼ã¨ã„ã„ã¾ã™ã€‚ã¾ãŸï¼Œãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã‚’å—ä¿¡ã™ã‚‹å´ã®ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆï¼ˆã‚³ãƒ³ã‚·ãƒ¥ãƒ¼ãƒžãƒ¼ï¼‰ã‚’ã‚µãƒ–ã‚¹ã‚¯ãƒ©ã‚¤ãƒãƒ¼ã¨ã„ã„ã¾ã™ã€‚ ãƒ‘ãƒ–ãƒªãƒƒã‚·ãƒ£ãƒ¼ã‹ã‚‰é€ä¿¡ã•ã‚ŒãŸãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã¯ï¼Œãƒˆãƒ”ãƒƒã‚¯ã¨ã„ã†é€ä¿¡å…ˆã«ç™»éŒ²ã•ã‚Œã¾ã™ã€‚ãƒˆãƒ”ãƒƒã‚¯ã«ç™»éŒ²ã•ã‚ŒãŸãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã¯ï¼Œãã®ãƒˆãƒ”ãƒƒã‚¯ã«å¯¾ã—ã¦é…ä¿¡ã‚’ç”³ã—è¾¼ã‚“ã§ã„ãŸä¸€ã¤ã¾ãŸã¯è¤‡æ•°ã®ã‚µãƒ–ã‚¹ã‚¯ãƒ©ã‚¤ãƒãƒ¼ã«é…ä¿¡ã•ã‚Œã¾ã™ã€‚ Pub/Subãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ãƒ³ã‚°ãƒ¢ãƒ‡ãƒ«ã§ã®ãƒ¡ãƒƒã‚»ãƒ¼
Itisango 2021/12/27
pubsub

architecture

http2

ã‚¢ãƒ¼ã‚ãƒ†ã‚¯ãƒãƒ£

ã‚ã¨ã§èªã‚€

server

client

pattern

model

system
ãƒªãƒ³ã‚¯
CompletableFuture (Java SE 17 & JDK 17)
Itisango 2021/09/12
â€œpublic class CompletableFuture<T> extends Object implements Future<T>, CompletionStage<T> A Future that may be explicitly completed (setting its value and status), and may be used as a CompletionStage, supporting dependent functions and actions that trigger upon its completion.â€

Java

HTTP

communication

network

API

async

HTTP2

concurrent

class

thread
ãƒªãƒ³ã‚¯
Goè¨€èªžãªã‚‰ãŸã£ãŸ20è¡Œã»ã©!!HTTP2å¯¾å¿œã‚µãƒ¼ãƒã®ä½œã‚Šæ–¹|TERAKOYA
Goè¨€èªžã‚’ä½¿ã£ã¦ã¨ã£ã¦ã‚‚ç°¡å˜ã«HTTP2ã«å¯¾å¿œã—ãŸWebã‚µãƒ¼ãƒã‚’æ§‹ç¯‰ã§ãã‚‹äº‹ã‚’çŸ¥ã‚Šã¾ã—ãŸã®ã§å‹‰å¼·ãŒã¦ã‚‰å®Ÿè£…ã—ã¦ã¿ã¾ã—ãŸã€‚ æœ¬å½“ã«ã¨ã£ã¦ã‚‚ç°¡å˜ã«å®Ÿè£…ã§ãã¾ã™ã€‚ ä½œã‚Šæ–¹ã®æ‰‹é †ä½œã‚Šæ–¹ã¯ä¸‹è¨˜ã®æµã‚Œã§ã™ã€‚ è¨¼æ˜Žæ›¸ãƒ»ç§˜å¯†éµã®å–å¾—Goæ¨™æº–ã®import net/httpã§Webã‚µãƒ¼ãƒã‚’æ§‹ç¯‰http.ListenAndServeã®ç®‡æ‰€ã‚’http.ListenAndServeTSLã«å¤‰æ›´ç’°å¢ƒã¡ãªã¿ã«ç§ã¯ä¸‹è¨˜ã®ç’°å¢ƒã§é–‹ç™ºã—ã¦ã„ã¾ã™ã€‚ Mac OS 10.12IntelliJ IDEA Community 2016.1go 1.7.1ãã‚Œã§ã¯é †ç•ªã«è¦‹ã¦ã„ãã¾ã—ã‚‡ã†ã€‚ ãƒ†ã‚¹ãƒˆç”¨ã‚µãƒ¼ãƒè¨¼æ˜Žæ›¸ãƒ»ç§˜å¯†éµã®ä½œæˆã‚¿ãƒ¼ãƒŸãƒŠãƒ«ã§/usr/local/go/src/crypto/tls/ã«ã‚ã‚‹generate_cert.go --host hostnameã‚’å®Ÿè¡Œã—ã¾ã™ã€‚ ã‚¿ãƒ¼ãƒŸãƒŠãƒ«ã§å®Ÿè¡Œ sudo go run /usr/loc
Itisango 2016/10/20
ãƒ—ãƒã‚°ãƒ©ãƒŸãƒ³ã‚°

Webåˆ¶ä½œ

ã‚µãƒ¼ãƒãƒ¼

ã‚ã¨ã§èªã‚€

HTTP2

ãƒã‚¿
ãƒªãƒ³ã‚¯
HTTP/2ãƒ—ãƒãƒˆã‚³ãƒ«ã«è¤‡æ•°ã®ã‚»ã‚ãƒ¥ãƒªãƒ†ã‚£å•é¡Œ--Black Hatã§ãƒ¬ãƒãƒ¼ãƒˆå…¬é–‹
Charlie OsborneÂ ï¼ˆSpecial to ZDNET.comï¼‰Â ç¿»è¨³æ ¡æ£ï¼šÂ ç·¨é›†éƒ¨ 2016-08-05 10:28 æ–°ã—ã„ãƒ—ãƒãƒˆã‚³ãƒ«ã§ã‚ã‚‹HTTP/2ã«ã€æ•°åƒä¸‡ã®ã‚¦ã‚§ãƒ–ã‚µã‚¤ãƒˆã‚’æ”»æ’ƒã®ãƒªã‚¹ã‚¯ã«æ™’ã™å¯èƒ½æ€§ãŒã‚ã‚‹è¤‡æ•°ã®ã‚»ã‚ãƒ¥ãƒªãƒ†ã‚£å•é¡ŒãŒç™ºè¦‹ã•ã‚ŒãŸã€‚ ã‚µã‚¤ãƒãƒ¼ã‚»ã‚ãƒ¥ãƒªãƒ†ã‚£ä¼šç¤¾Impervaã¯ç±³å›½æ™‚é–“8æœˆ3æ—¥ã€Black Hat USAã§ã‚¦ã‚§ãƒ–ã‚„é€šä¿¡ã‚·ã‚¹ãƒ†ãƒ ã§ä½¿ç”¨ã•ã‚Œã‚‹HTTPã®æœ€æ–°ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã‚ã‚‹HTTP/2ã«é–¢é€£ã—ã¦ã€è¤‡æ•°ã®é‡å¤§ãªã‚»ã‚ãƒ¥ãƒªãƒ†ã‚£ãƒ›ãƒ¼ãƒ«ãŒå˜åœ¨ã™ã‚‹ã¨å ±å‘Šã™ã‚‹ãƒ¬ãƒãƒ¼ãƒˆã‚’å…¬é–‹ã—ãŸã€‚ ã“ã®ãƒ¬ãƒãƒ¼ãƒˆã€ŒHTTP/2: In-depth analysis of the top four flaws of the next generation web protocolã€ã¯ã€HTTP/2ã«é–¢é€£ã™ã‚‹4ã¤ã®è„†å¼±æ€§ã¨æ”»æ’ƒæ‰‹æ³•ã«ã¤ã„ã¦èª¬æ˜Žã—ãŸã‚‚ã®ã ã€‚ç¾åœ¨ã€HTTP/2ã®å°Žå…¥æ•°ã¯ç€å®Ÿã«å¢—åŠ ã—ã¦
Itisango 2016/08/05
HTTP2

analysis

security

ã‚»ã‚ãƒ¥ãƒªãƒ†ã‚£

Apache

web

software
ãƒªãƒ³ã‚¯
ã€Œã‚¯ãƒ©ã‚¦ãƒ‰ã€HTTP/2ã€å¸¸æ™‚TLSæ™‚ä»£ã«æœ€é©åŒ–ã•ã‚ŒãŸHTTPã‚µãƒ¼ãƒãƒ¼ã‚’ç›®æŒ‡ã™ã€ï¼šNginxã‚ˆã‚Šé«˜é€Ÿã€HTTP/2ã‚µãƒ¼ãƒãƒ¼ã€ŒH2Oã€ - ï¼ IT
Nginxã‚ˆã‚Šé«˜é€Ÿã€HTTP/2ã‚µãƒ¼ãƒãƒ¼ã€ŒH2Oã€ï¼šã€Œã‚¯ãƒ©ã‚¦ãƒ‰ã€HTTP/2ã€å¸¸æ™‚TLSæ™‚ä»£ã«æœ€é©åŒ–ã•ã‚ŒãŸHTTPã‚µãƒ¼ãƒãƒ¼ã‚’ç›®æŒ‡ã™ã€ ã€Œã‚¯ãƒ©ã‚¦ãƒ‰ã€HTTP/2ã€å¸¸æ™‚TLSæ™‚ä»£ã«æœ€é©åŒ–ã•ã‚ŒãŸHTTPã‚µãƒ¼ãƒãƒ¼ã‚’ç›®æŒ‡ã™ã€ã¨ã„ã†HTTPã‚µãƒ¼ãƒãƒ¼ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³1.6ãŒãƒªãƒªãƒ¼ã‚¹ã•ã‚ŒãŸã€‚å‰ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒ™ãƒ³ãƒãƒžãƒ¼ã‚¯ã§ã¯Nginxã‚ˆã‚Šæ€§èƒ½ãŒé«˜ã„å ´é¢ã‚‚è¦‹å—ã‘ã‚‰ã‚Œã‚‹ã€‚ HTTP/2ã‚µãƒ¼ãƒãƒ¼ã€ŒH2Oã€ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³1.6ãŒ2015å¹´12æœˆ4æ—¥ã«ãƒªãƒªãƒ¼ã‚¹ã•ã‚ŒãŸã€‚ H2Oã¯ç¾åœ¨ãƒ‡ã‚£ãƒ¼ãƒ»ã‚¨ãƒŒãƒ»ã‚¨ãƒ¼ã«å‹¤ã‚ã‚‹å¥¥ä¸€ç©‚æ°ã‚’ä¸å¿ƒã«ã€2014å¹´ã‹ã‚‰é–‹ç™ºã•ã‚Œã¦ã„ã‚‹Webã‚µãƒ¼ãƒãƒ¼ã€‚ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã®ç›®çš„ã¨ã—ã¦ã€ã€Œã‚¯ãƒ©ã‚¦ãƒ‰ã€HTTP/2ã€å¸¸æ™‚TLSæ™‚ä»£ã«æœ€é©åŒ–ã•ã‚ŒãŸHTTPã‚µãƒ¼ãƒãƒ¼ã‚’ç›®æŒ‡ã™ã€ã¨ã—ã¦ã„ã‚‹ã€‚H2Oã¯MITãƒ©ã‚¤ã‚»ãƒ³ã‚¹ã‚’æŽ¡ç”¨ã—ãŸã‚ªãƒ¼ãƒ—ãƒ³ã‚½ãƒ¼ã‚¹ãƒ—ãƒãƒ€ã‚¯ãƒˆã§ã€ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã¯GitHubã§å…¬é–‹ã•ã‚Œã¦ã„ã‚‹ã€‚ H2Oã¯ã€HTTP/1.0ã€1.1ã«
Itisango 2015/12/08
ã‚ã¨ã§èªã‚€

HTTP2

HTTP

h2o

ã‚µãƒ¼ãƒ

æœ€é©åŒ–

2014å¹´

2015å¹´
ãƒªãƒ³ã‚¯
HTTP/2æ™‚ä»£ã®ã‚¦ã‚§ãƒ–ã‚µã‚¤ãƒˆè¨è¨ˆ
1. Copyright (C) 2015 DeNA Co.,Ltd. All Rights Reserved. HTTP/2æ™‚ä»£ã®ã‚¦ã‚§ãƒ–ã‚µã‚¤ãƒˆè¨è¨ˆ DeNA Â Co., Â Ltd. Kazuho Â Oku 1
Itisango 2015/08/21
http2

HTTP

Web

yapcasia

slide

è¨è¨ˆ

ã‚ã¨ã§èªã‚€
ãƒªãƒ³ã‚¯
libtrusterdã‚’Rustã§å‹•ã‹ã—ãŸ: misc
ãŠã¯ã‚ˆã†ã”ã–ã„ã¾ã™ã€‚å¥¥ã•ã‚“å‡ºå¼µä¸ã®æ¯åé”ã¨ã®å®Ÿå®¶ç”Ÿæ´»ã‚‚ãã‚ãã‚çµ‚äº†ã§ã™ã€‚kjunichiã§ã™ã€‚ TL;DR https://github.com/trusterd/libtrusterd/tree/master/examples/trusterd_rs åˆã‚ã« Rustã‚‚1.0ãŒãƒªãƒªãƒ¼ã‚¹ã•ã‚ŒãŸã‚Šã€rebuildfmã§ã‚‚RustãŒè©±é¡Œã«ãªã£ãŸå›žã‚‚ã‚ã£ãŸã®ã§ã€ã¾ãŸã€æ‡²ã‚Šãšã«ã‚„ã£ã¦ã¿ã‚‹ã“ã¨ã«ã—ãŸã€‚ libtrusterdã‚’Rustã§å‹•ã‹ãã†ã¨ã—ã¦å¦ã¹ãŸã“ã¨ Cã®æ–‡å—åˆ—ã‚’æ‰±ã† ä»¥å‰ã¯ã€ title.with_c_str(| title | unsafe { cvNamedWindow(title); } ã¨å¤‰æ›ã—ã¦ã„ãŸã¨ã“ã‚ã€1.0ä»¥é™ã¯ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã£ãŸã€‚ use with Gist Search Link https://doc.rust-lang.org/std/ffi/struct.C
Itisango 2015/07/17
mruby

rust

ã‚ã¨ã§èªã‚€

web

ãƒ—ãƒã‚°ãƒ©ãƒŸãƒ³ã‚°

http2

programming

development

software
ãƒªãƒ³ã‚¯
HTTP/2æ™‚ä»£ã®ãƒãƒƒã‚¯ã‚¨ãƒ³ãƒ‰é€šä¿¡æ¤œè¨Žãƒ¡ãƒ¢ - ã¼ã¡ã¼ã¡æ—¥è¨˜
1. ã¯ã˜ã‚ã«ã€ ä»Šæœã€ã“ã‚“ãªè¿”äº‹ã‚’å…ƒã« kazuho ã•ã‚“ã¨IPsec/TLSç‰ãƒãƒƒã‚¯ã‚¨ãƒ³ãƒ‰é€šä¿¡ã«ã¤ã„ã¦è°è«–ã™ã‚‹æ©Ÿä¼šã‚’å¾—ã¾ã—ãŸã€‚ ã›ã£ã‹ãã ã‹ã‚‰ç¾æ™‚ç‚¹ã§ã®è‡ªåˆ†ã®è€ƒãˆã‚’æ•´ç†ã—ã¦ãƒ¡ãƒ¢ã¨ã—ã¦æ®‹ã—ã¦ãŠãã¾ã™ã€‚ æ™®æ®µã¡ã‚ƒã‚“ã¨ã—ãŸã‚¹ãƒˆãƒ¼ãƒªã‚’ã‚‚ã£ãŸã‚¨ãƒ³ãƒˆãƒªãƒ¼ã—ã‹æ›¸ã„ã¦ã„ãªã„ã®ã§ã™ãŒã€ä»Šå›žã¯æ™‚é–“ãŒãªã„ã®ã§ã¡ã‚ƒã‚“ã¨ã—ãŸè«–ç†çš„æ–‡ç« ã«ãªã£ã¦ã„ãªã„ãƒ¡ãƒ¢ç¨‹åº¦ã®ã‚‚ã®ã§ã™ã€ã‚ã—ã‹ã‚‰ãšã€‚ ä»¥ä¸‹ã€ãƒ•ãƒãƒ³ãƒˆå´ã« HTTP/2 ã‚’å°Žå…¥ã—ãŸå ´åˆã®ãƒãƒƒã‚¯ã‚¨ãƒ³ãƒ‰é€šä¿¡ã‚’ã©ã†è€ƒãˆã‚‹ã‹ã®ãƒ¡ãƒ¢ã§ã™ã€‚ 2. æ€§èƒ½çš„è¦³ç‚¹ ãƒ•ãƒãƒ³ãƒˆã«HTTP/2ã‚’å°Žå…¥ã—ãŸã¨ã„ã†ã“ã¨ã¯ã€ãƒ–ãƒ©ã‚¦ã‚¶ã®HTTP HoLãƒ–ãƒãƒƒã‚¯è§£æ¶ˆãŒç›®çš„ã®ä¸€ã¤ã ã¨æ€ã†ã€‚HTTP/2ã®å¤šé‡åŒ–é€šä¿¡ã«ã‚ˆã£ã¦ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã‹ã‚‰ã“ã‚Œã¾ã§ä»¥ä¸Šã®åŒæ™‚ãƒªã‚¯ã‚¨ã‚¹ãƒˆã‚’ã•ã°ã‹ãªã„ã¨ã„ã‘ãªã„ï¼ˆã ã„ãŸã„åˆæœŸå€¤ã¯åŒæ™‚100æŽ¥ç¶šãã‚‰ã„ã«åˆ¶é™ã•ã‚Œã¦ã„ã‚‹ã¨æ€ã†ï¼‰ã€‚ ä»–æ–¹ãƒãƒƒã‚¯ã‚¨ãƒ³ãƒ‰å´é€šä¿¡ã¯ã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆå´ãŒãƒ–ãƒ©ã‚¦ã‚¶ã§ã¯ãª
Itisango 2015/07/16
HTTP2

2013å¹´

ã‚ã¨ã§èªã‚€

client
ãƒªãƒ³ã‚¯
ã€ŒHTTP/2ã€ãŒã¤ã„ã«ç™»å ´ï¼ é–‹ç™ºè€…ãŒçŸ¥ã£ã¦ãŠããŸã„é€šä¿¡ã®ä»•çµ„ã¿ãƒ»æ–°æ©Ÿèƒ½ãƒ»å°Žå…¥æ–¹æ³•
CodeZineç·¨é›†éƒ¨ã§ã¯ã€ç¾å ´ã§æ´»èºã™ã‚‹ãƒ‡ãƒ™ãƒãƒƒãƒ‘ãƒ¼ã‚’ã‚¹ã‚¿ãƒ¼ã«ã™ã‚‹ãŸã‚ã®ã‚«ãƒ³ãƒ•ã‚¡ãƒ¬ãƒ³ã‚¹ã€ŒDevelopers Summitã€ã‚„ã€ã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ã®ç”Ÿãã–ã¾ã‚’ãƒ–ãƒ¼ã‚¹ãƒˆã™ã‚‹ãŸã‚ã®ã‚¤ãƒ™ãƒ³ãƒˆã€ŒDevelopers Boostã€ãªã©ã€ã•ã¾ã–ã¾ãªã‚«ãƒ³ãƒ•ã‚¡ãƒ¬ãƒ³ã‚¹ã‚’ä¼ç”»ãƒ»é‹å–¶ã—ã¦ã„ã¾ã™ã€‚
Itisango 2015/06/22
HTTP2

2009å¹´

http

ãƒ—ãƒãƒˆã‚³ãƒ«

é–‹ç™º

web

programming

ã‚¤ãƒ³ã‚¿ãƒ¼ãƒãƒƒãƒˆ

é€šä¿¡
ãƒªãƒ³ã‚¯
HTTP 2.0 and QUIC - Protocols of the (near) future
HTTP 1.1 forced both developers and browser vendors to invent different tricks in order to make sites to load and run faster. HTTP 2.0 and QUIC will proâ€¦
Itisango 2014/09/21
http2

quic

slide

http

web

IT

2014å¹´

network

ãƒãƒƒãƒˆ
ãƒªãƒ³ã‚¯
Please admit defeat (was: Our Schedule) from Poul-Henning Kamp on 2014-05-26 ([email protected] from April to June 2014)
From: Poul-Henning Kamp <[email protected]> Date: Mon, 26 May 2014 06:34:25 +0000 To: HTTP Working Group <ietf [email protected]> Message-ID: <1282.1401086065@critter.freebsd.dk> In message <315A1736-1C33-403D-AC5F-6E488B880FAE@mnot.net>, Mark Nottingham wri tes: >The overwhelming preference expressed in the WG so far has been to work >to a tight schedule. HTTP/3 has already been discussed a bit, be
Itisango 2014/06/01
http://news.mynavi.jp/news/2014/05/28/055/

2015å¹´

http2

WWW

3C

HTTP

ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯

ãƒ‹ãƒ¥ãƒ¼ã‚¹

2014å¹´

W3C

protocol
ãƒªãƒ³ã‚¯
HTTP/2.0ã‚’æ¨ã¦ã€ã‚ˆã‚Šå®Œç’§ãªãƒ—ãƒãƒˆã‚³ãƒ«ã‚’ - W3C WGã§Varnishé–‹ç™ºè€…ãŒææ¡ˆ
W3C HTTPãƒ¯ãƒ¼ã‚ãƒ³ã‚°ã‚°ãƒ«ãƒ¼ãƒ—ã®ãƒ¡ãƒ¼ãƒªãƒ³ã‚°ãƒªã‚¹ãƒˆã«ã€ŒPlease admit defeat (was: Our Schedule)ã€ã¨ã„ã†ãƒ¡ãƒ¼ãƒ«ãŒæŠ•å‡½ã•ã‚ŒãŸã€‚ãƒ¡ãƒ¼ãƒ«ã‚’æŠ•å‡½ã—ãŸã®ã¯é«˜é€Ÿã‚ãƒ£ãƒƒã‚·ãƒ¥ã‚µãƒ¼ãƒVarnishã®é–‹ç™ºè€…ã§ã‚ã‚ŠFreeBSDã®ã‚«ãƒ¼ãƒãƒ«é–‹ç™ºè€…ã§ã‚‚ã‚ã‚‹Poul-Henning Kampæ°ã€‚ä¸å®Œå…¨ãªçŠ¶æ…‹ã®HTTP/2.0ã‚’å…¬é–‹ã™ã‚‹ã“ã¨ã¯ã•ã¾ã–ã¾ãªãƒªã‚½ãƒ¼ã‚¹ã®ç„¡é§„ã§ã‚ã‚‹ã“ã¨ã€HTTPã®ã‚³ãƒ³ã‚»ãƒ—ãƒˆã‚’ã‚ˆã‚Šã‚·ãƒ³ãƒ—ãƒ«ã«ã—ã¦æš—å·å‡¦ç†ã‚„ãƒ—ãƒ©ã‚¤ãƒã‚·ãªã©ã®å•é¡Œã‚’è§£æ±ºã—ãŸã€ã—ã£ã‹ã‚Šã—ãŸãƒ—ãƒãƒˆã‚³ãƒ«ã‚’ç–å®šã—ã¦ã‹ã‚‰å…¬é–‹ã™ã¹ãã ã¨ææ¡ˆã—ã¦ã„ã‚‹ã€‚ HTTP/2.0ã¯Googleã®é–‹ç™ºã—ãŸSPDYã¨å‘¼ã°ã‚Œã‚‹ãƒ—ãƒãƒˆã‚³ãƒ«ã‚’ãƒ™ãƒ¼ã‚¹ã¨ã—ãŸæ¬¡ä¸–ä»£ã®HTTPãƒ—ãƒãƒˆã‚³ãƒ«ã€‚ç¾åœ¨ç–å®šãŒé€²ã‚ã‚‰ã‚Œã¦ã„ã‚‹æ®µéšŽã«ã‚ã‚Šã€é †èª¿ã«ã„ã‘ã°2015å¹´ã«ã¯æ£å¼ãªãƒ—ãƒãƒˆã‚³ãƒ«ã¨ã—ã¦ç–å®šã•ã‚Œã‚‹è¦‹é€šã—ã€‚ã—ã‹ã—ç¾åœ¨ç–å®šãŒé€²ã‚ã‚‰ã‚Œã¦ã„ã‚‹HTTP/2.0ã¯ã„ã
Itisango 2014/06/01
http://lists.w3.org/Archives/Public/ietf-http-wg/2014AprJun/0815.html

2015å¹´

http2

WWW

3C

HTTP

ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯

ãƒ‹ãƒ¥ãƒ¼ã‚¹

2014å¹´

W3C

protocol
ãƒªãƒ³ã‚¯
1