@hydranium/data-client-theia 1.0.0-next.204 → 1.0.0-next.206
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -16,10 +16,10 @@ import type { FrontendApplicationContribution, OnWillStopAction } from '@theia/c
|
|
|
16
16
|
*
|
|
17
17
|
* **Stop.** {@link onStop} disposes every tracked session, which sends its
|
|
18
18
|
* `closeSession`, so the server ends it as closed: each document it was the
|
|
19
|
-
* last to hold
|
|
19
|
+
* last to hold is released at once. Otherwise the server learns of the page only
|
|
20
20
|
* when its connection goes, which Theia may hold open for its reconnect
|
|
21
21
|
* timeout, and then ends the sessions as lost, so their documents wait out the
|
|
22
|
-
*
|
|
22
|
+
* release grace. The close is best effort: under load the page's last frames
|
|
23
23
|
* can be lost on the way, and the server then ends the sessions as lost. A
|
|
24
24
|
* session with calls still in flight at the stop closes after them, which is
|
|
25
25
|
* too late for a page going away, and is left to the server's connection-close
|
|
@@ -24,10 +24,10 @@ const inversify_1 = require("@theia/core/shared/inversify");
|
|
|
24
24
|
*
|
|
25
25
|
* **Stop.** {@link onStop} disposes every tracked session, which sends its
|
|
26
26
|
* `closeSession`, so the server ends it as closed: each document it was the
|
|
27
|
-
* last to hold
|
|
27
|
+
* last to hold is released at once. Otherwise the server learns of the page only
|
|
28
28
|
* when its connection goes, which Theia may hold open for its reconnect
|
|
29
29
|
* timeout, and then ends the sessions as lost, so their documents wait out the
|
|
30
|
-
*
|
|
30
|
+
* release grace. The close is best effort: under load the page's last frames
|
|
31
31
|
* can be lost on the way, and the server then ends the sessions as lost. A
|
|
32
32
|
* session with calls still in flight at the stop closes after them, which is
|
|
33
33
|
* too late for a page going away, and is left to the server's connection-close
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@hydranium/data-client-theia",
|
|
3
|
-
"version": "1.0.0-next.
|
|
3
|
+
"version": "1.0.0-next.206",
|
|
4
4
|
"description": "Theia-coupled client primitives for the hydranium data-server protocol head; companion of @hydranium/data-server. Bridges framework typed errors (e.g. ConflictError) across Theia's RPC boundary so their code + data survive the wire.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"hydranium",
|
|
@@ -73,8 +73,8 @@
|
|
|
73
73
|
"watch": "tsc -b -w --preserveWatchOutput"
|
|
74
74
|
},
|
|
75
75
|
"devDependencies": {
|
|
76
|
-
"@hydranium/client-theia": "1.0.0-next.
|
|
77
|
-
"@hydranium/protocol": "1.0.0-next.
|
|
76
|
+
"@hydranium/client-theia": "1.0.0-next.206",
|
|
77
|
+
"@hydranium/protocol": "1.0.0-next.206",
|
|
78
78
|
"@theia/core": "^1.70.0",
|
|
79
79
|
"@theia/workspace": "^1.70.0",
|
|
80
80
|
"@types/node": "^22.0.0",
|
|
@@ -85,8 +85,8 @@
|
|
|
85
85
|
"vscode-jsonrpc": "9.0.1"
|
|
86
86
|
},
|
|
87
87
|
"peerDependencies": {
|
|
88
|
-
"@hydranium/client-theia": "1.0.0-next.
|
|
89
|
-
"@hydranium/protocol": "1.0.0-next.
|
|
88
|
+
"@hydranium/client-theia": "1.0.0-next.206",
|
|
89
|
+
"@hydranium/protocol": "1.0.0-next.206",
|
|
90
90
|
"@theia/core": "^1.70.0",
|
|
91
91
|
"@theia/workspace": "^1.70.0",
|
|
92
92
|
"inversify": "^6.0.0",
|
|
@@ -21,10 +21,10 @@ import { injectable } from '@theia/core/shared/inversify';
|
|
|
21
21
|
*
|
|
22
22
|
* **Stop.** {@link onStop} disposes every tracked session, which sends its
|
|
23
23
|
* `closeSession`, so the server ends it as closed: each document it was the
|
|
24
|
-
* last to hold
|
|
24
|
+
* last to hold is released at once. Otherwise the server learns of the page only
|
|
25
25
|
* when its connection goes, which Theia may hold open for its reconnect
|
|
26
26
|
* timeout, and then ends the sessions as lost, so their documents wait out the
|
|
27
|
-
*
|
|
27
|
+
* release grace. The close is best effort: under load the page's last frames
|
|
28
28
|
* can be lost on the way, and the server then ends the sessions as lost. A
|
|
29
29
|
* session with calls still in flight at the stop closes after them, which is
|
|
30
30
|
* too late for a page going away, and is left to the server's connection-close
|