The WHATWG Blog — Progressing Streams
Please leave your sense of logic at the door, thanks! Progressing Streams July 5th, 2017 by Adam Rice in What's Next Back in 2014 we announced the Streams Standard. It's about time for an update on where we are and what's coming up. Streaming the response to fetch() via the response.body attribute was standardized last year and is now implemented in several major browsers. Recently streaming uploa
ストリーム処ç†ã¨ã¯ä½•ã‹ï¼Ÿï¼‹2016å¹´ã®å‡ºæ¥äº‹ - Qiita
ãã®å¯¾å‡¦ã§å…¨éƒ¨ã«å¯¾å¿œã™ã‚‹ã®ã¯ç„¡ç†ãªã‚“ã˜ã‚ƒãªã„ã®ï¼Ÿ Watermarkã€Triggerã€Accumulationã®æ©Ÿæ§‹ãŒå°Žå…¥ã•ã‚Œã‚Œã°ã‚¹ãƒˆãƒªãƒ¼ãƒ 処ç†ã¯å…¨ã¦å¯¾å¿œå¯èƒ½ã‹ã¨ã„ã†ã¨ã€ ãã‚“ãªã“ã¨ã¯ã‚ã‚Šã¾ã›ã‚“。 何故ãªã‚‰ã€ä¸‹è¨˜ã®ã‚ˆã†ãªå•é¡ŒãŒç™ºç”Ÿã—ã¦ãã‚‹ã‹ã‚‰ã§ã™ã€‚ Watermarkを実時刻ã‹ã‚‰ã©ã‚Œãらã„é…らã›ã¦è¨å®šã™ã‚Œã°ã„ã„ã®ã‹ï¼Ÿ é…れを大ããã™ã‚Œã°æ£ç¢ºæ€§ã¯å¢—ã—ã¾ã™ãŒã€é…延時間ã¯å¤§ãããªã‚Šã¾ã™ã€‚ Accumulationã®ãŸã‚ã«ã‚¦ã‚£ãƒ³ãƒ‰ã‚¦ã®é›†è¨ˆçµæžœã‚’ã©ã‚Œã ã‘ä¿æŒã™ã‚Œã°ã„ã„ã®ã‹ï¼Ÿ ä¿æŒã™ã‚‹æ™‚é–“ãŒé•·ã„ã»ã©ã€ã‚¹ãƒˆãƒªãƒ¼ãƒ 処ç†ã‚’è¡Œã†ã‚·ã‚¹ãƒ†ãƒ ã®ãƒªã‚½ãƒ¼ã‚¹ãŒå¿…è¦ã¨ãªã‚Šã¾ã™ã€‚ データ処ç†ã‚·ã‚¹ãƒ†ãƒ （ãƒãƒƒãƒã€ã‚¹ãƒˆãƒªãƒ¼ãƒ å«ã‚€ï¼‰ã«ã¯ä¸‹è¨˜ã®ï¼“è¦ç´ ã®ãƒˆãƒ¬ãƒ¼ãƒ‰ã‚ªãƒ•ãŒã‚ã‚‹ã¨ã•ã‚Œã¦ã„ã¾ã™ã€‚ 完全性(Completeness) 低é…延(Low Latency) 低コスト(Low Cost) ã“ã®ï¼“è¦ç´ ã‚’å…¨ã¦ã«æº€ãŸã™ã“ã¨ã¯å‡ºæ¥ãšã€å…¨ã¦ã®ãƒ‡ãƒ¼ã‚¿
Stream API入門 - Qiita
Nodeã®ã‚¢ãƒ‰ãƒ™ãƒ³ãƒˆã‚«ãƒ¬ãƒ³ãƒ€ãƒ¼ã€æ—¢ã«çµ‚ã‚ã£ãŸæž ãŒç©ºã„ã¦ã„ã¦ã€ã“ã®éš›æ›¸ããŸã„ãƒã‚¿ãŒã‚ã£ãŸã‚“ã§å‚åŠ ã—ã¾ã—ãŸã€‚宜ã—ããŠé¡˜ã„ã—ã¾ã™ã€‚ アドベントカレンダーã®æ™‚期ã ã‘出没ã™ã‚‹å¼±ã„日曜Haskellerã§ã™ã€‚普段ã®å®Ÿå‹™ã§ã¯Node.jsã«ãŠä¸–話ã«ãªã£ã¦ã¾ã™ã€‚宜ã—ããŠé¡˜ã„ã—ã¾ã™ã€‚ ã•ã¦ã€ã¿ãªã•ã‚“Stream API使ã£ã¦ã¾ã™ã‹ï¼ŸNode.jsã¨ã„ã£ãŸã‚‰éžåŒæœŸã§ã™ã‚ˆãã€ã‚„ã£ã±ã‚Šã€‚ã—ã‹ã—ãªãŒã‚‰ã€JavaScriptã§ã‚‚ä»–ã®è¨€èªžã§ã‚‚ã€éžåŒæœŸå‡¦ç†è‡ªä½“ã¯æ³¨ç›®ã•ã‚Œã¦ã„ã‚‹ã‚‚ã®ã®ã€ã¾ã experimentalã¨ã„ã†æ„Ÿã˜ã§æ§˜ã€…ãªAPIãŒè€ƒæ¡ˆã•ã‚Œã¦ã¯æ¶ˆãˆã¦ã„ãã€ã¾ãŸå…ƒã€…ãã†ã„ã†æ–‡åŒ–ãŒæ ¹å¼·ããªã‹ã£ãŸã¨ã“ã‚ã‹ã‚‰æ¥ãŸäººãŸã¡ã«ã¨ã£ã¦ã€ã“ã†ã„ã†æ–‡åŒ–ã¯ã¡ã‚‡ã£ã¨ç«‹ã¡å…¥ã‚Šã¥ã‚‰ã„ã¨ã“ã‚ã‚‚ã‚ã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“ã。 今日ã¯ã€ä¸»ã«ãã†ã„ã†äººãŸã¡ã«å‘ã‘ã¦ã€ã¾ãšéžåŒæœŸã®è‰²ã€…ãªAPIã®ç´¹ä»‹ã€ãã—ã¦ãã®ä¸ã§ã®ã‚¹ãƒˆãƒªãƒ¼ãƒ ã®ãƒ¡ãƒªãƒƒãƒˆã€ãã—ã¦å®Ÿéš›ã®Stream
highWaterMarkã‹ã‚‰æŽ¢ã‚‹Node.jsã®Streamã®ä»•çµ„ã¿
ãƒ¤ãƒ•ãƒ¼æ ªå¼ä¼šç¤¾ã¯ã€2023å¹´10月1æ—¥ã«LINEãƒ¤ãƒ•ãƒ¼æ ªå¼ä¼šç¤¾ã«ãªã‚Šã¾ã—ãŸã€‚LINEãƒ¤ãƒ•ãƒ¼æ ªå¼ä¼šç¤¾ã®æ–°ã—ã„ブãƒã‚°ã¯ã“ã¡ã‚‰ã§ã™ã€‚LINEヤフー Tech Blog ã“ã‚“ã«ã¡ã¯ã€‚Node.js 言語サãƒãƒ¼ãƒˆãƒãƒ¼ãƒ ã®æŸ„澤å²ä¹Ÿ (@fmy) ã§ã™ã€‚ 12/6ã®ã‚¨ãƒ³ãƒˆãƒªã€Œä»Šå¹´ã®ã†ã¡ã«å¯¾å¿œã—ãŸã„ã€Node.jsã®Bufferã«æ½œã‚€å±é™ºæ€§ã€ã«å¼•ã続ãã€ç¤¾å†…ã§ã® Node.js Core API 勉強会ã®å†…容を紹介ã—ã¾ã™ã€‚ 1. Stream API ã®é‡è¦æ€§ Node.js 界隈ã®æœ‰åãªè¨€è‘‰ã«æ¬¡ã®ã‚ˆã†ãªã‚‚ã®ãŒã‚ã‚Šã¾ã™ã€‚ 「Stream を制ã™ã‚‹ã‚‚ã®ã¯ã€ Node.js を制ã™ã€ Node.js 最大ã®ç‰¹å¾´ã¯ä½•ã¨è¨€ã£ã¦ã‚‚éžåŒæœŸ I/O ã§ã™ã€‚ ãã—ã¦ãã®éžåŒæœŸ I/O ã®å®Ÿè£…ã“ã㌠stream モジュールãªã®ã§ã™ã€‚ HTTP サーãƒã®ãƒªã‚¯ã‚¨ã‚¹ãƒˆãƒ»ãƒ¬ã‚¹ãƒãƒ³ã‚¹ gulp ã®ã‚ˆã†ãªã‚¿ã‚¹ã‚¯ãƒ©ãƒ³ãƒŠãƒ¼ TCP ソケ
stream b/w node.js and whatwg // Speaker Deck
Talk about Stream API difference between node.js and whatwg at #tng11 2016/08/08
Fetch ã§ã® Stream を用ã„ãŸãƒ—ãƒã‚°ãƒ¬ã‚¹å–å¾—ã¨ã‚ャンセル | blog.jxck.io
Intro WHATWG ãŒå®šç¾©ã™ã‚‹ Fetch API ã¯ã€å‡ºãŸã°ã‹ã‚Šã®ä»•æ§˜ã§ã¯ã€é€”ä¸ã§ã®ã‚ャンセルやã€ãƒ—ãƒã‚°ãƒ¬ã‚¹ã‚¤ãƒ™ãƒ³ãƒˆã®å–å¾—ãŒå«ã¾ã‚Œã¦ã„ãªã‹ã£ãŸã€‚ ã—ã‹ã—ã€å¾Œã®æ›´æ–°ã§ fetch çµæžœã® Response Body ㌠WHATWG Stream API を実装ã™ã‚‹ã“ã¨ã«ãªã£ãŸãŸã‚ã€ç¾åœ¨ã®ä»•æ§˜ã§ã¯ãƒ—ãƒã‚°ãƒ¬ã‚¹ã‚’å–ã‚‹ã“ã¨ã‚‚ã‚ャンセルをã™ã‚‹ã“ã¨ã‚‚å¯èƒ½ã¨ãªã£ã¦ã„る。 今回ã¯ã€ã“ã†ã—㟠API ã®ã‚¢ãƒƒãƒ—デートã«ã¤ã„ã¦è¨˜ã™ã€‚ Update 最åˆã®å…¬é–‹æ™‚ã«ã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ã«æ›¸ã„ã¦ã„ãŸã€‚ 「XHR ã§ã¯ã§ãる㌠Fetch ã§ã¯ã§ããªã„ã€ã“ã¨ãŒã€ä»•æ§˜ä¸Šã¯ç„¡ããªã£ãŸã“ã¨ã‚’æ„味ã™ã‚‹ã€‚ ã—ã‹ã—ã€ç¾æ™‚点ã§ä»•æ§˜ã¨ã—ã¦ã¾ã 出æ¥ãªã„ã“ã¨ãŒã‚ã‚‹ã“ã¨ãŒåˆ¤æ˜Žã—ãŸã€‚ Upload ã® Progress ã“ã‚Œã«ä¼´ã„ã€è¨˜äº‹ã®ä¸€éƒ¨ã‚’ä¿®æ£ã—ãŸã€‚ Fetch 最新㮠Fetch ã®ä»•æ§˜ã¯ä»¥ä¸‹ã§ç¢ºèªã§ãる。 Fetch Spec 仕様
Stream Your Way to Immediate Responses  | Blog  | Chrome for Developers
Anyone who's used service workers could tell you that they’re asynchronous all the way down. They rely exclusively on event-based interfaces, like FetchEvent, and use promises to signal when asynchronous operations are complete. Asynchronicity is equally important, albeit less visible to the developer, when it comes to responses provided by a service worker's fetch event handler. Streaming respons
History Of Streams
The history of streamscontentsprehistory (streams before a stream api)streams 1summer of streams, userland vs corestreams2 (one step forward, 2 steps back)streams3conclusionprehistoryin node.js’s early days back in 2010, the node.js website featured an example of a tcp echo server. on feb 9th, 2010 the tcp stream’s events were named “receive†and “eofâ€. Shorly later, by feb 18th, 2010 those events
Streams - Kevin Lawler
January 2016 Streams & Spikes The notion of a "stream" has been around for a while, but for some reason I haven't seen it generalized, even though it would be extremely natural to do so. For our current purposes a stream will be any ongoing or repeated process: a habit can be a stream, for example. This won't be the full definition. We'll want to be able to hang a few connotations on it as well, b
2016 - the year of web streams - JakeArchibald.com
Yeah, ok, it's a touch bold to talk about something being the thing of the year as early as January, but the potential of the web streams API has gotten me all excited. TL;DR: Streams can be used to do fun things like turn clouds to butts, transcode MPEG to GIF, but most importantly, they can be combined with service workers to become the fastest way to serve content. Streams, huh! What are they g
Fetch-with-Streams-jp
ã“ã®ãƒ–ラウザ ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ã‚µãƒãƒ¼ãƒˆã¯çµ‚了ã—ã¾ã—ãŸã€‚サãƒãƒ¼ãƒˆã•ã‚Œã¦ã„るブラウザã«ã‚¢ãƒƒãƒ—グレードã—ã¦ãã ã•ã„。
That's so fetch!
There's been some confusion around the new fetch API recently. Let's clear things up. The first thing you'll notice about fetch is it's a massive improvement on XMLHttpRequest in terms of API design. Here's how to get some JSON using XHR: var xhr = new XMLHttpRequest(); xhr.open('GET', url); xhr.responseType = 'json'; xhr.onload = function () { console.log(xhr.response); }; xhr.onerror = function
Fetch + Streams Demo
This demo will search the first billion digits of PI for a substring you specify, and tell you the position at which it was found. It will do this without consuming a billion bytes of memory! That was impossible with XHR! Furthermore, it won't even need to do text decoding and string comparison, as it will operate on the bytes directly. (XHR's pseudo-streaming mode, with an ever-growing responseTe
Reactive Streamsã¨ã¯ï¼Ÿ - ãŸã‘ãžã†ç€•æ»ãƒ–ãƒã‚°
Reactive Streamsã¨ã„ã†ã®ã¯ãƒŽãƒ³ãƒ–ãƒãƒƒã‚ングãªback pressureå¯èƒ½ãªéžåŒæœŸã‚¹ãƒˆãƒªãƒ¼ãƒ 処ç†ã®æ¨™æº–çš„ãªä»•æ§˜ã‚’æä¾›ã—よã†ã¨ã„ã†ã‚‚ã®ã§ã€å®Ÿè£…ã¨ã—ã¦ã¯Akka Streamsã€RxJavaã€Reactor Composableã€Ratpackãªã©ãŒã‚ã‚Šã¾ã™ã€‚ Reactive Streamsã«ã¤ã„ã¦ã¯Akkaã®ã‚³ãƒŸãƒƒã‚¿ã§ã‚ã‚‹Konrad Malawskiã•ã‚“ã®ä»¥ä¸‹ã®ã‚¹ãƒ©ã‚¤ãƒ‰ãŒã¨ã¦ã‚‚ã‚ã‹ã‚Šã‚„ã™ã„ã§ã™ã€‚ 2014 akka-streams-tokyo-japanese from Konrad Malawski ストリーム処ç†ï¼ˆã¨ã„ã†ã‹éžåŒæœŸãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ãƒ³ã‚°å…¨èˆ¬ã«è¨€ãˆã‚‹ã“ã¨ã§ã™ãŒï¼‰ã§ã¯å—ä¿¡å´ã®å‡¦ç†èƒ½åŠ›ã‚’超ãˆã‚‹ãƒ‡ãƒ¼ã‚¿ã‚’é€ä¿¡ã—続ã‘ã‚‹ã¨ã„ãšã‚Œã‚ャパシティを超ãˆã¦ã‚ªãƒ¼ãƒãƒ¼ãƒ•ãƒãƒ¼ãŒç™ºç”Ÿã—ã¦ã—ã¾ã†ãŸã‚ã€é€ä¿¡å´ã«æ¯”ã¹ã¦å—ä¿¡å´ã®å‡¦ç†èƒ½åŠ›ãŒä½Žã„å ´åˆã¯é€ä¿¡å´ãŒæ‰‹åŠ 減ã—ã¦ãƒ‡ãƒ¼ã‚¿ã‚’é€ä¿¡ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ãª
WHATWG Streams APIã«ã¤ã„ã¦ã®ãƒ¡ãƒ¢ - maru source
ã“ã‚“ã«ã¡ã¯ä¸¸å±±@h13i32maruã§ã™ã€‚ WHATWG Streams APIã‚’å°‘ã—触ã£ã¦ã¿ãŸã®ã§ã€ãã®ãƒ¡ãƒ¢ã§ã™ã€‚ ドã‚ュメント WHATWG Streams ã“ã®ãƒ¡ãƒ¢ã¯Last Updated 21 January 2015ã‚’å…ƒã«æ›¸ã„㟠whatwg/streams サンプルやリファレンス実装ãªã©ãŒã‚ã‚‹ ã“ã®ãƒ¡ãƒ¢ã¯commit 879902ã‚’å…ƒã«æ›¸ã„㟠Stream APIãŒãƒ–ラウザã«ã‚„ã£ã¦ãã‚‹ @jxckã•ã‚“ãŒnodeã®Stream APIã¨çµ¡ã‚ã¦WHATWGã®Streams APIを紹介ã—ã¦ã„ã‚‹ 概念 JavaScriptã®ãƒ—ãƒã‚°ãƒ©ãƒ ä¸ã§å‡¦ç†ã™ã‚‹(大ãã‚ãª)データã®èªã¿æ›¸ãを統一的ã«æ‰±ã†ãŸã‚ã®ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹ã‚’Streams APIã¨ã—ã¦WHATWGãŒç–定ã—ã¦ã„る。例ãˆã°XHRã§å¤§ããªãƒ•ã‚¡ã‚¤ãƒ«ã‚’èªã¿è¾¼ã‚“ã 時ã«ã¯ã™ã¹ã¦ã®ãƒ‡ãƒ¼ã‚¿ã‚’èªã¿è¾¼ã‚“ã ã‚ã¨ã«ã‚³ãƒ¼ãƒ«ãƒãƒƒã‚¯ãŒå‘¼ã°ã‚Œã‚‹*1。ã“ã‚Œã ã¨èªã¿
Functional Reactive Programming with the Power of Node.js Streams - RisingStack Engineering
The goal of this article is not to go into the very details of Functional Reactive Programming. It’s more about getting you interested in Node.jsNode.js is an asynchronous event-driven JavaScript runtime and is the most effective when building scalable network applications. Node.js is free of locks, so there's no chance to dead-lock any process. streams and the concept of functional reactive progr
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
The Definitive TypeScript Guide - Blog | SitePen
Reactive Streams 入門 #jjug
Intent to Ship: Long Task API - Google Groups
ECMAScript7を見æ®ãˆãŸã€JavaScript(TypeScript)ã§ä½¿ãˆã‚‹FRPライブラリã®æ¯”較調査 - Qiita
{{#tags}}- {{label}}
{{/tags}}