parsek-cdp-server 0.1.0__tar.gz

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.
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright [yyyy] [name of copyright owner]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
@@ -0,0 +1,139 @@
1
+ Metadata-Version: 2.4
2
+ Name: parsek-cdp-server
3
+ Version: 0.1.0
4
+ Summary: Parsek CDP server — launch, supervise and proxy a browser; server-side feature producers.
5
+ Author: xa1era
6
+ License-Expression: Apache-2.0
7
+ Project-URL: Repository, https://github.com/xa1era/parsek-cdp
8
+ Requires-Python: >=3.13
9
+ Description-Content-Type: text/markdown
10
+ License-File: LICENSE
11
+ Requires-Dist: parsek-cdp~=0.1.0
12
+ Requires-Dist: aiohttp>=3.9
13
+ Requires-Dist: psutil>=5
14
+ Requires-Dist: prometheus-client>=0.19
15
+ Dynamic: license-file
16
+
17
+ # parsek-cdp-server
18
+
19
+ The server side of **parsek-cdp**: launching, supervising and proxying a
20
+ browser, plus the server-side feature *producers* that digest raw CDP into
21
+ `Parsek.*` events.
22
+
23
+ A separate distribution from `parsek-cdp` (the client); installed via
24
+ `pip install parsek-cdp[server]`. It depends on `parsek-cdp` and reuses its
25
+ shared layers wholesale — the generated `cdp` protocol, the `core` primitives
26
+ (`CDPConnection`, `Target`, `DataType`) and the `parsek` contract — adding only
27
+ what must live next to the browser.
28
+
29
+ > Документация на русском: [README.ru.md](README.ru.md).
30
+
31
+ ## Running
32
+
33
+ ```python
34
+ import asyncio
35
+ from parsek_cdp_server import ParsekServer
36
+ from parsek_cdp.features import RequestListener
37
+
38
+
39
+ async def main():
40
+ server = ParsekServer(idle_timeout=300) # a browser self-closes after 5 min idle
41
+ server.register_feature(RequestListener) # make the feature selectable via ?feature=
42
+ await server.start("127.0.0.1", 9333)
43
+ try:
44
+ await asyncio.Event().wait() # keep the server alive
45
+ finally:
46
+ await server.stop()
47
+
48
+
49
+ asyncio.run(main())
50
+ ```
51
+
52
+ A client connects to this server with
53
+ `Browser.get_distant_browser("http://127.0.0.1:9333", ...)` — the API is
54
+ identical to a local browser (see the client README). Every `POST /browsers`
55
+ spins up its own supervised browser; `idle_timeout` (on the server or in the
56
+ request body) closes a browser that sits with no connection.
57
+
58
+ ### Where the browser comes from
59
+
60
+ `launcher` finds a Chromium-compatible binary on its own. By default it walks
61
+ the usual install paths; the `PARSEK_CHROMES_PATH` env var (directories
62
+ separated by `os.pathsep`, like `PATH`) overrides the search — each launch picks
63
+ a **random** one of the browsers it finds (a cheap way to spread load and
64
+ fingerprints). An explicit path and flags go through `LaunchOptions`
65
+ (`executable`, `headless`, `extra_args`, ...) — either on the server or
66
+ per-request in the `POST /browsers` body.
67
+
68
+ ## Modules
69
+
70
+ | Module | Responsibility |
71
+ | --- | --- |
72
+ | `launcher` | Start Chrome/Chromium, wait for the DevTools endpoint, read the browser-level websocket from `/json/version`. |
73
+ | `supervisor` | Browser lifecycle: health, crash detection, restart, idle shutdown, and `Parsek.browserStateChanged` broadcast. |
74
+ | `proxy` | Accept client websockets and bridge each 1:1 to a Chrome target; host feature producers and serve the `Parsek.*` surface. |
75
+ | `metrics` | Prometheus exposition at `/metrics`. |
76
+ | `reaper` | A separate subprocess that kills leaked (zombie/orphaned) parsek-launched Chrome processes. |
77
+
78
+ ## Connection model
79
+
80
+ As in the client, **every target gets its own websocket** (no `sessionId`
81
+ multiplexing). One parsing flow = one `browser_context`; pages within it each
82
+ connect over their own websocket. The proxy bridges a page's client socket to
83
+ the corresponding Chrome socket **1:1**.
84
+
85
+ ## Endpoints
86
+
87
+ ```
88
+ HTTP POST /browsers create a task -> browser_uuid
89
+ HTTP GET /metrics Prometheus metrics
90
+ ws /cdp/{browser_uuid}/control browser-level pipe + Parsek.browserStateChanged
91
+ ws /cdp/{browser_uuid}/page/{target_id} CDP proxy (per-page) + Parsek.*
92
+ ```
93
+
94
+ The control channel is a raw pipe to the browser endpoint plus the
95
+ `Parsek.browserStateChanged` broadcast, so a parser learns when its browser
96
+ crashed/restarted instead of hanging; browser-level CDP (creating/disposing
97
+ contexts, etc.) passes straight through it.
98
+
99
+ ## Features
100
+
101
+ The server is **pure passthrough** by default (`ParsekServer` has no `features`
102
+ argument). Feature producers are added with `register_feature(...)` and selected
103
+ per browser with `POST /browsers?feature=<name>`. On a page pipe a producer
104
+ digests the raw CDP burst into a couple of aggregated `Parsek.*` events and
105
+ *suppresses* the raw events it consumed; `?raw=1` opts out of suppression.
106
+
107
+ ## Metrics (`GET /metrics`)
108
+
109
+ | Metric | Type | What |
110
+ | --- | --- | --- |
111
+ | `parsek_browsers` | gauge | number of supervised browsers |
112
+ | `parsek_targets{browser,type}` | gauge | targets per browser, by type |
113
+ | `parsek_nested_targets{browser}` | gauge | nested targets (with a `parentId`) |
114
+ | `parsek_browser_cpu_percent{browser}` | gauge | CPU% of the browser process tree |
115
+ | `parsek_browser_memory_bytes{browser}` | gauge | RSS of the browser process tree |
116
+ | `parsek_cdp_events_total{browser,target,domain}` | counter | CDP events by target and domain |
117
+
118
+ Targets and CPU/RAM are sampled by a background task (polling `/json/list` +
119
+ `psutil`), so a scrape only reads cached values and does not block the event
120
+ loop. The event counter is labelled by target id — series for dead targets are
121
+ pruned on every snapshot.
122
+
123
+ ## Zombie reaper
124
+
125
+ On start the server spawns a **separate subprocess** (`reaper`) that
126
+ periodically scans for Chrome processes we launched (recognised by the
127
+ `--user-data-dir=…parsek-cdp-…` marker) that became zombies or orphans
128
+ (`ppid == 1`), and kills them along with their subtree. Controlled by
129
+ `ParsekServer(reap_zombies=..., reap_interval=...)`; it can also be run by hand:
130
+ `python -m parsek_cdp_server.reaper --once`.
131
+
132
+ ## Notes
133
+
134
+ The `Parsek.*` contract lives in the client distribution (`parsek_cdp.parsek`)
135
+ and is shared by both sides.
136
+
137
+ ## License
138
+
139
+ Apache-2.0.
@@ -0,0 +1,123 @@
1
+ # parsek-cdp-server
2
+
3
+ The server side of **parsek-cdp**: launching, supervising and proxying a
4
+ browser, plus the server-side feature *producers* that digest raw CDP into
5
+ `Parsek.*` events.
6
+
7
+ A separate distribution from `parsek-cdp` (the client); installed via
8
+ `pip install parsek-cdp[server]`. It depends on `parsek-cdp` and reuses its
9
+ shared layers wholesale — the generated `cdp` protocol, the `core` primitives
10
+ (`CDPConnection`, `Target`, `DataType`) and the `parsek` contract — adding only
11
+ what must live next to the browser.
12
+
13
+ > Документация на русском: [README.ru.md](README.ru.md).
14
+
15
+ ## Running
16
+
17
+ ```python
18
+ import asyncio
19
+ from parsek_cdp_server import ParsekServer
20
+ from parsek_cdp.features import RequestListener
21
+
22
+
23
+ async def main():
24
+ server = ParsekServer(idle_timeout=300) # a browser self-closes after 5 min idle
25
+ server.register_feature(RequestListener) # make the feature selectable via ?feature=
26
+ await server.start("127.0.0.1", 9333)
27
+ try:
28
+ await asyncio.Event().wait() # keep the server alive
29
+ finally:
30
+ await server.stop()
31
+
32
+
33
+ asyncio.run(main())
34
+ ```
35
+
36
+ A client connects to this server with
37
+ `Browser.get_distant_browser("http://127.0.0.1:9333", ...)` — the API is
38
+ identical to a local browser (see the client README). Every `POST /browsers`
39
+ spins up its own supervised browser; `idle_timeout` (on the server or in the
40
+ request body) closes a browser that sits with no connection.
41
+
42
+ ### Where the browser comes from
43
+
44
+ `launcher` finds a Chromium-compatible binary on its own. By default it walks
45
+ the usual install paths; the `PARSEK_CHROMES_PATH` env var (directories
46
+ separated by `os.pathsep`, like `PATH`) overrides the search — each launch picks
47
+ a **random** one of the browsers it finds (a cheap way to spread load and
48
+ fingerprints). An explicit path and flags go through `LaunchOptions`
49
+ (`executable`, `headless`, `extra_args`, ...) — either on the server or
50
+ per-request in the `POST /browsers` body.
51
+
52
+ ## Modules
53
+
54
+ | Module | Responsibility |
55
+ | --- | --- |
56
+ | `launcher` | Start Chrome/Chromium, wait for the DevTools endpoint, read the browser-level websocket from `/json/version`. |
57
+ | `supervisor` | Browser lifecycle: health, crash detection, restart, idle shutdown, and `Parsek.browserStateChanged` broadcast. |
58
+ | `proxy` | Accept client websockets and bridge each 1:1 to a Chrome target; host feature producers and serve the `Parsek.*` surface. |
59
+ | `metrics` | Prometheus exposition at `/metrics`. |
60
+ | `reaper` | A separate subprocess that kills leaked (zombie/orphaned) parsek-launched Chrome processes. |
61
+
62
+ ## Connection model
63
+
64
+ As in the client, **every target gets its own websocket** (no `sessionId`
65
+ multiplexing). One parsing flow = one `browser_context`; pages within it each
66
+ connect over their own websocket. The proxy bridges a page's client socket to
67
+ the corresponding Chrome socket **1:1**.
68
+
69
+ ## Endpoints
70
+
71
+ ```
72
+ HTTP POST /browsers create a task -> browser_uuid
73
+ HTTP GET /metrics Prometheus metrics
74
+ ws /cdp/{browser_uuid}/control browser-level pipe + Parsek.browserStateChanged
75
+ ws /cdp/{browser_uuid}/page/{target_id} CDP proxy (per-page) + Parsek.*
76
+ ```
77
+
78
+ The control channel is a raw pipe to the browser endpoint plus the
79
+ `Parsek.browserStateChanged` broadcast, so a parser learns when its browser
80
+ crashed/restarted instead of hanging; browser-level CDP (creating/disposing
81
+ contexts, etc.) passes straight through it.
82
+
83
+ ## Features
84
+
85
+ The server is **pure passthrough** by default (`ParsekServer` has no `features`
86
+ argument). Feature producers are added with `register_feature(...)` and selected
87
+ per browser with `POST /browsers?feature=<name>`. On a page pipe a producer
88
+ digests the raw CDP burst into a couple of aggregated `Parsek.*` events and
89
+ *suppresses* the raw events it consumed; `?raw=1` opts out of suppression.
90
+
91
+ ## Metrics (`GET /metrics`)
92
+
93
+ | Metric | Type | What |
94
+ | --- | --- | --- |
95
+ | `parsek_browsers` | gauge | number of supervised browsers |
96
+ | `parsek_targets{browser,type}` | gauge | targets per browser, by type |
97
+ | `parsek_nested_targets{browser}` | gauge | nested targets (with a `parentId`) |
98
+ | `parsek_browser_cpu_percent{browser}` | gauge | CPU% of the browser process tree |
99
+ | `parsek_browser_memory_bytes{browser}` | gauge | RSS of the browser process tree |
100
+ | `parsek_cdp_events_total{browser,target,domain}` | counter | CDP events by target and domain |
101
+
102
+ Targets and CPU/RAM are sampled by a background task (polling `/json/list` +
103
+ `psutil`), so a scrape only reads cached values and does not block the event
104
+ loop. The event counter is labelled by target id — series for dead targets are
105
+ pruned on every snapshot.
106
+
107
+ ## Zombie reaper
108
+
109
+ On start the server spawns a **separate subprocess** (`reaper`) that
110
+ periodically scans for Chrome processes we launched (recognised by the
111
+ `--user-data-dir=…parsek-cdp-…` marker) that became zombies or orphans
112
+ (`ppid == 1`), and kills them along with their subtree. Controlled by
113
+ `ParsekServer(reap_zombies=..., reap_interval=...)`; it can also be run by hand:
114
+ `python -m parsek_cdp_server.reaper --once`.
115
+
116
+ ## Notes
117
+
118
+ The `Parsek.*` contract lives in the client distribution (`parsek_cdp.parsek`)
119
+ and is shared by both sides.
120
+
121
+ ## License
122
+
123
+ Apache-2.0.
@@ -0,0 +1,46 @@
1
+ """parsek-cdp-server -- the server scope: launch, supervise and proxy a browser.
2
+
3
+ Separate distribution from ``parsek-cdp`` (the client); installed via
4
+ ``pip install parsek-cdp[server]``. It *depends on* ``parsek-cdp`` and reuses
5
+ its shared layers wholesale -- the generated ``cdp`` protocol, the ``core``
6
+ primitives (``CDPConnection``, ``Target``, ``DataType``) and the ``parsek``
7
+ contract -- adding only what must live next to the browser:
8
+
9
+ * :mod:`~parsek_cdp_server.launcher` -- spawn Chrome, find its websocket;
10
+ * :mod:`~parsek_cdp_server.supervisor` -- own the browser lifecycle: health,
11
+ crash detection, restart, idle shutdown, and ``Parsek.browserStateChanged``
12
+ broadcast;
13
+ * :mod:`~parsek_cdp_server.proxy` -- accept client websockets and bridge
14
+ each one 1:1 to a Chrome target (no ``sessionId`` multiplexing, no id remap),
15
+ hosting feature producers on page pipes and serving the ``Parsek.*`` surface;
16
+ * :mod:`~parsek_cdp_server.metrics` -- Prometheus exposition at ``/metrics``
17
+ (browsers, targets/types, nested targets, per-target CDP events, CPU/RAM);
18
+ * :mod:`~parsek_cdp_server.reaper` -- a separate subprocess that kills leaked
19
+ (zombie/orphaned) parsek-launched Chrome processes.
20
+
21
+ Feature *producers* (raw CDP -> ``Parsek.*``) are shared code shipped in the
22
+ client distribution (:mod:`parsek_cdp.features`); the server hosts them but does
23
+ not define them. ``ParsekServer`` registers none by default -- it is a pure
24
+ passthrough until features are added via ``register_feature``.
25
+
26
+ Endpoints (see :mod:`~parsek_cdp_server.proxy`)::
27
+
28
+ HTTP POST /browsers create task -> browser_uuid
29
+ HTTP GET /metrics Prometheus metrics
30
+ ws /cdp/{browser_uuid}/control lifecycle + Parsek.*
31
+ ws /cdp/{browser_uuid}/page/{target_id} CDP proxy (per-target) + Parsek.*
32
+ """
33
+
34
+ from __future__ import annotations
35
+
36
+ from .launcher import ChromeLauncher
37
+ from .metrics import ServerMetrics
38
+ from .proxy import ParsekServer
39
+ from .supervisor import BrowserSupervisor
40
+
41
+ __all__ = [
42
+ "ParsekServer",
43
+ "ChromeLauncher",
44
+ "BrowserSupervisor",
45
+ "ServerMetrics",
46
+ ]