7 API の変更 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 34.1.8 Updating Client and Service . . . . . . . . . . . . . . . . . . . . . . . 210 34.2 Working With AIDL Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 XIV 並行性：PM 348 62 ようこそ 349 63 Async の基礎 350 63.1 async/await . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 63.2 Future . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 64 チャネルと制御フロー 354 64.1 Async チャネル . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 64.2 Join . . . . .

............................ 108 Chapter.5 - Async Function ................................................................................... 116 Async Functionとは .................................. ....................................................... 116 Async Functionの構文 ..................................................................................... 119 await 式 ....................... .................................................................................... 121 Async Functionと配列 ..................................................................................... 124 Promises

setTimeout(function () { resolve('Async Hello world'); }, 16); }); } asyncFunction().then(function (value) { console.log(value); // => 'Async Hello world' }).catch(function (error) でエラーとなった場合の コールバックを設定しています。 このpromiseオブジェクトはsetTimeoutで16ms後にresolveされるので、 そのタイミング で then のコールバックが呼ばれ 'Async Hello world' と出力されます。 8 JavaScript Promiseの本 この場合 catch のコールバックは呼ばれることはないですが、 setTimeout が存在しな Promises - Thinking Sync in an Async World // Speaker Deck15 というスライドではPromiseの状態遷移について分 かりやすく書かれています。 15 https://speakerdeck.com/kerrick/javascript-promises-thinking-sync-in-an-async-world 10 JavaScript Promiseの本

schedule. 2. Chunkserverl Responsible for data storage l Multi-replicas consistency 3. The client l Provides read and write data interfaces for upper-layer applications l Interacts with MDS chunk.Client 1. CurveBS client provides services by libCurve. At first, external processes such as QEMU, Cinder, and NBD use it to access storage services provided by Curve. The client provids application must be restarted every time the library is updated. To solve this problem, the CurveBS Client has been optimized to decouple the application from libcurve and add a NEBD module to join the

this example. @startuml concise "Client" as Client concise "Server" as Server concise "Response freshness" as Cache Server is idle Client is idle @Client 0 is send Client -> Server@+25 : GET +25 is await await +75 is recv +25 is idle +25 is send Client -> Server@+25 : GET\nIf-Modified-Since: 150 +25 is await +50 is recv +25 is idle @100 <-> @275 : no need to re-request from server @Server 25 is recv +25 +25 is work +25 is send Server -> Client@+25 : 200 OK\nExpires: 275 +25 is idle +75 is recv +25 is send Server -> Client@+25 : 304 Not Modified +25 is idle @Cache 75 is fresh +200 is stale @enduml PlantUML

this example. @startuml concise "Client" as Client concise "Server" as Server concise "Response freshness" as Cache Server is idle Client is idle @Client 0 is send Client -> Server@+25 : GET +25 is await await +75 is recv +25 is idle +25 is send Client -> Server@+25 : GET\nIf-Modified-Since: 150 +25 is await +50 is recv +25 is idle @100 <-> @275 : no need to re-request from server @Server 25 is recv +25 +25 is work +25 is send Server -> Client@+25 : 200 OK\nExpires: 275 +25 is idle +75 is recv +25 is send Server -> Client@+25 : 304 Not Modified +25 is idle @Cache 75 is fresh +200 is stale @enduml PlantUML

10 タイミング図 @startuml concise "Client" as Client concise "Server" as Server concise "Response freshness" as Cache Server is idle Client is idle @Client 0 is send Client -> Server@+25 : GET +25 is await await +75 is recv +25 is idle +25 is send Client -> Server@+25 : GET\nIf-Modified-Since: 150 +25 is await +50 is recv +25 is idle @100 <-> @275 : no need to re-request from server @Server 25 is recv +25 +25 is work +25 is send Server -> Client@+25 : 200 OK\nExpires: 275 +25 is idle +75 is recv +25 is send Server -> Client@+25 : 304 Not Modified +25 is idle @Cache 75 is fresh +200 is stale @enduml 10.17

10 タイミング図 @startuml concise "Client" as Client concise "Server" as Server concise "Response freshness" as Cache Server is idle Client is idle @Client 0 is send Client -> Server@+25 : GET +25 is await await +75 is recv +25 is idle +25 is send Client -> Server@+25 : GET\nIf-Modified-Since: 150 +25 is await +50 is recv +25 is idle @100 <-> @275 : no need to re-request from server @Server 25 is recv +25 +25 is work +25 is send Server -> Client@+25 : 200 OK\nExpires: 275 +25 is idle +75 is recv +25 is send Server -> Client@+25 : 304 Not Modified +25 is idle @Cache 75 is fresh +200 is stale @enduml 10.17

的なインターフェース ifupdown V:608, I:979 199 設 定::ifupdown ネットワークを接続したり切断したりする標準化 されたツール (Debian 特定) isc-dhcp-client V:217, I:981 2875 設定:: 低レ ベル DHCP クライアント pppoeconf V:0, I:5 186 設定:: ヘル パー PPPoE コネクションの設定ヘルパー files?:” に対して”Yes” を選択します。 ”/etc/exim4/passwd.client” を編集しスマートホストのためのパスワードエントリーを作成します。 $ sudo vim /etc/exim4/passwd.client ... $ cat /etc/exim4/passwd.client ^smtp.*\.hostname\.dom:username@hostname.dom:password テムリソースの消費を最小限とした exim4(8) (optional) 以下のようにして exim4 を起動します。 $ sudo systemctl start exim4 ”/etc/exim4/passwd.client” 中のホスト名はエイリアスであってはいけません。真のホスト名は以下のよう にして確認できます。 $ host smtp.hostname.dom smtp.hostname.dom is an

10 タイミング図 @startuml concise "Client" as Client concise "Server" as Server concise "Response freshness" as Cache Server is idle Client is idle @Client 0 is send Client -> Server@+25 : GET +25 is await await +75 is recv +25 is idle +25 is send Client -> Server@+25 : GET\nIf-Modified-Since: 150 +25 is await +50 is recv +25 is idle @100 <-> @275 : no need to re-request from server @Server 25 is recv +25 +25 is work +25 is send Server -> Client@+25 : 200 OK\nExpires: 275 +25 is idle +75 is recv +25 is send Server -> Client@+25 : 304 Not Modified +25 is idle @Cache 75 is fresh +200 is stale @enduml 10.17