You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: testapps/libevent_http_server/readme.md
+92-1Lines changed: 92 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,8 @@
3
3
## Command
4
4
5
5
```
6
-
$ mkdir build && cd build && make -j
6
+
$ mkdir build && cd build && cmake .. && make -j
7
+
$ # curl http://localhost:8080/http-client
7
8
```
8
9
9
10
### Thanks
@@ -21,3 +22,93 @@ $ mkdir build && cd build && make -j
21
22
22
23

23
24
25
+
## Introduction for pinpoint on asynchronous framework
26
+
27
+
> what's problem in asynchronous framework (event driver)?
28
+
29
+
In synchronous, we gets trace by it's called order, that is the logical order when handling request, but in asynchronous framework, trace are driven by event, it's the event order. So, we must find a way to recover the logical order.
30
+
31
+
### Synchronous call flow
32
+
33
+

34
+
35
+
### Asynchronous call flow
36
+
37
+
> Red line: user A logical flow \
38
+
Blue line: user B logical flow
39
+
40
+

41
+
42
+
Here is the question, how to separate A and B from mixed call chains ?
While, there are many unknown cases in below list. If you have any question, [create an issue 🙋♂️ ](https://github.com/pinpoint-apm/pinpoint-c-agent/issues/new).
0 commit comments