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
| Status description | string | Short description of the status. ||
40
+
| Error | string | Short description of the error . ||
41
+
| Seq | string | Correlation number. Request and response must have the same seq number. ||
42
+
| Body | ANY | Contains the properties of the command. ||
28
43
29
44
Known commands:
30
45
31
-
| Code | Name |
32
-
| ---- | --------------------------- |
33
-
| 0 | HEARBEAT_REQUEST |
34
-
| 1 | HEARTBEAT_RESPONSE |
35
-
| 2 | HELLO_REQUEST |
36
-
| 3 | HELLO_RESPONSE |
37
-
| 4 | SUBSCRIBE_REQUEST |
38
-
| 5 | SUBSCRIBE_RESPONSE |
39
-
| 6 | ASYNC_MESSAGE_TO_CLIENT |
40
-
| 7 | ASYNC_MESSAGE_TO_CLIENT_ACK |
41
-
| 8 | ADD_BRIDGE_REQUEST |
42
-
| 9 | ADD_BRIDGE_RESPONSE |
43
-
| 11 | DISCONNECT_REQUEST |
44
-
| 12 | DISCONNECT_RESPONSE |
46
+
| Code | Name |
47
+
| ---- | ------------------------------------ |
48
+
| 0 | HEARBEAT_REQUEST |
49
+
| 1 | HEARTBEAT_RESPONSE |
50
+
| 2 | HELLO_REQUEST |
51
+
| 3 | HELLO_RESPONSE |
52
+
| 4 | SUBSCRIBE_REQUEST |
53
+
| 5 | SUBSCRIBE_RESPONSE |
54
+
| 6 | ASYNC_MESSAGE_TO_CLIENT |
55
+
| 7 | ASYNC_MESSAGE_TO_CLIENT_ACK |
56
+
| 8 | ADD_BRIDGE_REQUEST |
57
+
| 9 | ADD_BRIDGE_RESPONSE |
58
+
| 10 | ASYNC_MESSAGE_TO_SERVER |
59
+
| 11 | DISCONNECT_REQUEST |
60
+
| 12 | DISCONNECT_RESPONSE |
61
+
| 13 | ASYNC_MESSAGE_TO_CLIENT_ACK_RESPONSE |
62
+
| 14 | PUBLISH_MESSAGE_REQUEST |
63
+
| 15 | PUBLISH_MESSAGE_RESPONSE |
45
64
46
65
Known status:
47
66
@@ -54,26 +73,68 @@ Known status:
54
73
55
74
## Commands
56
75
57
-
### Heartbeat
76
+
### Heartbeat request
77
+
78
+
*Request* : HEARBEAT_REQUEST.
79
+
*Response* : HEARTBEAT_RESPONSE.
80
+
81
+
Heartbeat request are sent by client to check the availablity of an EventMesh Server.
82
+
83
+
### Hello request
84
+
85
+
*Request* : HELLO_REQUEST.
86
+
*Response* : HELLO_RESPONSE.
87
+
88
+
Client send hello request to EventMesh server to create a session.
89
+
The following informations are passed in the request. They are used by the EventMesh server to check if the client is authorized to subscribe or publish.
| Environment | string | Environment used by the client. Possible values can be TST,VAL or PRD |
95
+
| Urn | string | URN of the EventMesh server calling an another EventMesh server. |
96
+
| Port | int32 | Port of the EventMesh server calling an another EventMesh server. |
97
+
| Password | string | Password of the client. Used during the authentication phase. |
98
+
| BufferCloudEvents | int32 | Number of messages sent to the client. Used to send a batch of messages. |
99
+
| Purpose | int32 | Type of session. Possible values are : SUBSCRIBE = 0, PUBLISH = 1 |
100
+
| IsServer | boolean | Indicate if the request is coming from a client or a server. |
101
+
| Pid | int32 | Identifier of the process. |
102
+
103
+
> [!WARNING]
104
+
> When a bridge is created between two EventMesh servers. The parameters `Urn` and `Port` will be used to transmit messages from one server to the second and to the client.
105
+
106
+
When a session is created, an hello response is sent by the EventMesh server to the client.
107
+
It contains a unique session identifier. This value will be used by the client to perform future operations.
0 commit comments