concurrent-c-node 0.4.1__tar.gz → 0.6.0__tar.gz

{concurrent_c_node-0.4.1 → concurrent_c_node-0.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: concurrent-c-node
-Version: 0.4.1
+Version: 0.6.0
 Summary: JavaScript and npm packages from Python over the Concurrent-C bridge: one spawned Node child per domain, host-controlled lifetime.
 License: MIT
 Project-URL: Repository, https://github.com/sreekotay/concurrent-c
@@ -17,6 +17,10 @@ Part of [Concurrent-C](https://github.com/sreekotay/concurrent-c) — a
 strict C11-superset preprocessor: `.ccs` lowers to plain C and compiles
 with your host C compiler.  (This bridge itself is pure Python.)
 
+Map of the three boundaries (CC hosts Python, native modules, this
+package bridge):
+[JS / Python interop](https://github.com/sreekotay/concurrent-c/blob/main/docs/js-py-modules.md).
+
 ```python
 import cc_node
 
@@ -57,6 +61,11 @@ Import stays `import cc_node`. Examples ship in the wheel. The mirror of
   the handle ledger and `release()` drops one early; `destroy()` is
   idempotent, every door answers `bridge is closed` after, and the
   child dies with the bridge (and on host exit, via stdin EOF).
+  Teardown is **cooperative** (farewell `close` + drain, then wait /
+  kill-fallback): in-flight calls may still return a correct value.
+  Hard child death (`SIGKILL`, `process.abort`) is a different contract —
+  in-flight ops must reject. See
+  [`bridge_stress.md`](https://github.com/sreekotay/concurrent-c/blob/main/stress/bridge/bridge_stress.md).
 
 ## Async is free
 
@@ -157,10 +166,13 @@ A worked tour (builtin Node modules, chains, callbacks, thenables,
 buffers — no npm install needed):
 `python -m cc_node.examples.use_node`.
 
-Adversarial multi-child storm (fanout, callback blizzard, shm hail,
-teardown derby): [`stress/bridge/`](https://github.com/sreekotay/concurrent-c/tree/main/stress/bridge)
-— `./stress/bridge/run.sh` (`CHAOS_SCALE=full` for bigger N; latency demos
-stay in `cc_node/examples/`).
+Adversarial multi-child storm (escaped closures, cooperative
+fanout-destroy, abort inject, handle-leak / RSS soaks):
+[`stress/bridge/`](https://github.com/sreekotay/concurrent-c/tree/main/stress/bridge)
+— `./stress/bridge/run.sh` (`CHAOS_SCALE=full` / `soak` for bigger N).
+Mode catalog + destroy contracts:
+[`bridge_stress.md`](https://github.com/sreekotay/concurrent-c/blob/main/stress/bridge/bridge_stress.md)
+(latency demos stay in `cc_node/examples/`).
 
 And when the hot path is YOUR code rather than an npm package, skip the
 wire entirely: a page of Concurrent-C (or C) exports as a native module

{concurrent_c_node-0.4.1 → concurrent_c_node-0.6.0}/README.md

@@ -6,6 +6,10 @@ Part of [Concurrent-C](https://github.com/sreekotay/concurrent-c) — a
 strict C11-superset preprocessor: `.ccs` lowers to plain C and compiles
 with your host C compiler.  (This bridge itself is pure Python.)
 
+Map of the three boundaries (CC hosts Python, native modules, this
+package bridge):
+[JS / Python interop](https://github.com/sreekotay/concurrent-c/blob/main/docs/js-py-modules.md).
+
 ```python
 import cc_node
 
@@ -46,6 +50,11 @@ Import stays `import cc_node`. Examples ship in the wheel. The mirror of
   the handle ledger and `release()` drops one early; `destroy()` is
   idempotent, every door answers `bridge is closed` after, and the
   child dies with the bridge (and on host exit, via stdin EOF).
+  Teardown is **cooperative** (farewell `close` + drain, then wait /
+  kill-fallback): in-flight calls may still return a correct value.
+  Hard child death (`SIGKILL`, `process.abort`) is a different contract —
+  in-flight ops must reject. See
+  [`bridge_stress.md`](https://github.com/sreekotay/concurrent-c/blob/main/stress/bridge/bridge_stress.md).
 
 ## Async is free
 
@@ -146,10 +155,13 @@ A worked tour (builtin Node modules, chains, callbacks, thenables,
 buffers — no npm install needed):
 `python -m cc_node.examples.use_node`.
 
-Adversarial multi-child storm (fanout, callback blizzard, shm hail,
-teardown derby): [`stress/bridge/`](https://github.com/sreekotay/concurrent-c/tree/main/stress/bridge)
-— `./stress/bridge/run.sh` (`CHAOS_SCALE=full` for bigger N; latency demos
-stay in `cc_node/examples/`).
+Adversarial multi-child storm (escaped closures, cooperative
+fanout-destroy, abort inject, handle-leak / RSS soaks):
+[`stress/bridge/`](https://github.com/sreekotay/concurrent-c/tree/main/stress/bridge)
+— `./stress/bridge/run.sh` (`CHAOS_SCALE=full` / `soak` for bigger N).
+Mode catalog + destroy contracts:
+[`bridge_stress.md`](https://github.com/sreekotay/concurrent-c/blob/main/stress/bridge/bridge_stress.md)
+(latency demos stay in `cc_node/examples/`).
 
 And when the hot path is YOUR code rather than an npm package, skip the
 wire entirely: a page of Concurrent-C (or C) exports as a native module

{concurrent_c_node-0.4.1 → concurrent_c_node-0.6.0}/concurrent_c_node.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: concurrent-c-node
-Version: 0.4.1
+Version: 0.6.0
 Summary: JavaScript and npm packages from Python over the Concurrent-C bridge: one spawned Node child per domain, host-controlled lifetime.
 License: MIT
 Project-URL: Repository, https://github.com/sreekotay/concurrent-c
@@ -17,6 +17,10 @@ Part of [Concurrent-C](https://github.com/sreekotay/concurrent-c) — a
 strict C11-superset preprocessor: `.ccs` lowers to plain C and compiles
 with your host C compiler.  (This bridge itself is pure Python.)
 
+Map of the three boundaries (CC hosts Python, native modules, this
+package bridge):
+[JS / Python interop](https://github.com/sreekotay/concurrent-c/blob/main/docs/js-py-modules.md).
+
 ```python
 import cc_node
 
@@ -57,6 +61,11 @@ Import stays `import cc_node`. Examples ship in the wheel. The mirror of
   the handle ledger and `release()` drops one early; `destroy()` is
   idempotent, every door answers `bridge is closed` after, and the
   child dies with the bridge (and on host exit, via stdin EOF).
+  Teardown is **cooperative** (farewell `close` + drain, then wait /
+  kill-fallback): in-flight calls may still return a correct value.
+  Hard child death (`SIGKILL`, `process.abort`) is a different contract —
+  in-flight ops must reject. See
+  [`bridge_stress.md`](https://github.com/sreekotay/concurrent-c/blob/main/stress/bridge/bridge_stress.md).
 
 ## Async is free
 
@@ -157,10 +166,13 @@ A worked tour (builtin Node modules, chains, callbacks, thenables,
 buffers — no npm install needed):
 `python -m cc_node.examples.use_node`.
 
-Adversarial multi-child storm (fanout, callback blizzard, shm hail,
-teardown derby): [`stress/bridge/`](https://github.com/sreekotay/concurrent-c/tree/main/stress/bridge)
-— `./stress/bridge/run.sh` (`CHAOS_SCALE=full` for bigger N; latency demos
-stay in `cc_node/examples/`).
+Adversarial multi-child storm (escaped closures, cooperative
+fanout-destroy, abort inject, handle-leak / RSS soaks):
+[`stress/bridge/`](https://github.com/sreekotay/concurrent-c/tree/main/stress/bridge)
+— `./stress/bridge/run.sh` (`CHAOS_SCALE=full` / `soak` for bigger N).
+Mode catalog + destroy contracts:
+[`bridge_stress.md`](https://github.com/sreekotay/concurrent-c/blob/main/stress/bridge/bridge_stress.md)
+(latency demos stay in `cc_node/examples/`).
 
 And when the hot path is YOUR code rather than an npm package, skip the
 wire entirely: a page of Concurrent-C (or C) exports as a native module

{concurrent_c_node-0.4.1 → concurrent_c_node-0.6.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "concurrent-c-node"
-version = "0.4.1"
+version = "0.6.0"
 description = "JavaScript and npm packages from Python over the Concurrent-C bridge: one spawned Node child per domain, host-controlled lifetime."
 readme = "README.md"
 requires-python = ">=3.8"