commit 183477048326a176c3cd86cf94c4940887b1c48f
author danzh <danzh@google.com> Fri Jun 21 11:15:12 2019 -0700
committer Copybara-Service <copybara-worker@google.com> Fri Jun 21 13:05:27 2019 -0700
tree aead002b5031fcc0dcc90aec95bdfd9830653fd4
parent 5d880a9181904af003f06262b899e3e50efcfdad

gfe-relnote: n/a(doc change) Update third_party/quic/platform/api/README.md.

Replace DOT graph with raw textual graph because DOT graph is not supported by googlesource nor in chromium.

PiperOrigin-RevId: 254432994
Change-Id: Iae83254673dab51a3c8a9ebe0fee7f7e37c68db6

quic/platform/api/README.md

diff --git a/quic/platform/api/README.md b/quic/platform/api/README.md
index d3de2e1..117e424 100644
--- a/quic/platform/api/README.md
+++ b/quic/platform/api/README.md
@@ -13,43 +13,48 @@
 
     Most APIs are used by QUIC core to interact with platform infrastructure
     (i.e. QUIC_LOG) or to wrap around platform dependent data types (i.e.
-    QuicIntervalSet), the dependency is:
+    QuicThread), the dependency is:
 
-    ```dot
-    digraph {
-    application -> quic_core -> quic_platform_api -> quic_platform_impl -> platform_infrastructure
-    application -> platform_infrastructure
-    }
-    ```
+```
+application -> quic_core -> quic_platform_api
+      |                             |
+      v                             v
+platform_infrastructure <- quic_platform_impl
+```
 
 -   APIs used by applications:
 
     Some APIs are used by applications to interact with QUIC core (i.e.
     QuicMemSlice). For such APIs, their dependency model is:
 
-    ```dot
-    digraph {
-    application -> quic_platform_impl -> platform_infrastructure
-    application -> quic_core -> quic_platform_api
-    quic_platform_impl -> quic_platform_api
-    application -> platform_infrastructure
-    }
-    ```
+```
+application -> quic_core -> quic_platform_api
+    |                            ^
+    |                            |
+     -------------------> quic_platform_impl
+    |                            |
+    |                            v
+     -------------------> platform_infrastructure
+```
 
-    An example for such dependency is QuicClock.
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;An example for such dependency
+is QuicClock.
 
-    Or
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Or
 
-    ```dot
-    digraph {
-    application -> quic_platform_impl -> platform_infrastructure
-    application -> quic_core -> quic_platform_api -> quic_platform_impl
-    quic_platform_impl -> quic_platform_api
-    application -> platform_infrastructure
-    }
-    ```
+```
+application -> quic_core -> quic_platform_api
+    |                            ^
+    |                            |
+    |                            v
+     -------------------> quic_platform_impl
+    |                            |
+    |                            v
+     -------------------> platform_infrastructure
+```
 
-    An example for such dependency is QuicMemSlice.
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;An example for such dependency
+is QuicMemSlice.
 
 # Documentation of each API and its usage.