Skip to content

Commit 502d131

Browse files
author
Joone Hur
committed
docs(README): update links to live examples
1 parent 7a74436 commit 502d131

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ The following sections will analyze each area with examples. All examples involv
117117

118118
The following example code demonstrates how a long-running task on a worker thread can block subsequent messages in its task queue.
119119

120-
[Link to live demo](https://joone.github.io/web/explainers/delayed_messages/long_task/)
120+
[Link to live example](https://wicg.github.io/delayed-message-timing/examples/long-task)
121121

122122
### index.html
123123

@@ -212,7 +212,7 @@ Another challenge is when the target context's task queue becomes overloaded wit
212212
This example demonstrates how task queues in web workers can become congested when tasks take longer to process than the rate at which
213213
messages are sent. It sends delete tasks every 30ms, then a read task, measuring queue wait times to show the congestion effect.
214214

215-
[Link to live example](https://joone.github.io/web/explainers/delayed_messages/congested/)
215+
[Link to live example](https://wicg.github.io/delayed-message-timing/examples/congested/)
216216

217217
### index.html
218218

@@ -334,7 +334,7 @@ When data is sent using `postMessage()`, it undergoes serialization by the sende
334334

335335
The following example code demonstrate the delay introduced by serializing/deserializing a large JSON object during `postMessage()`.
336336

337-
[Link to live demo](https://joone.github.io/web/explainers/delayed_messages/serialization/)
337+
[Link to live example](https://wicg.github.io/delayed-message-timing/examples/serialization/)
338338

339339

340340
### index.html

0 commit comments

Comments
 (0)