4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	eaec209a37	Stop the stdio channel holding its lock across a pipe write, so a refused subscribe cannot deadlock it (issue 1286)	2026-10-19 21:51:13 +02:00
jochen	ec80dcfc22	0.1.13: one rule for taking an event, and no handler left by a refused subscribe (hq issue 276) ... A handler takes an event by returning and asks for it again by throwing; any mesh/event answer but an error is taken. Written down in the README where event handling is, with what follows for a handler: throw only when the work was not done, and be safe to run twice. Both SDKs added the handler before asking the runtime and kept it when the runtime refused, so a module that asks again until it is taken (every Go consumer does) ran its handler once per attempt for every event. A refused subscribe now removes its handler; one the Go runtime did not answer in time is kept, since the runtime may have bound it.	2026-10-06 18:14:58 +02:00
jochen	81ca305ddd	The Go SDK subscribes and asks through the runtime (hq ADR 0198) ... Subscribe(pattern, handler) asks the runtime for the module's events and answers each mesh/event only after the matching handlers returned nil, so the runtime acknowledges it on the bus then and not before; Ask(key, body) calls a tool as the module. Topic matching is the TypeScript SDK's.	2026-10-03 23:19:54 +02:00
jochen	b95448be60	The Go SDK serves as the module the runtime names, answers calls concurrently, and emits through the runtime (hq ADR 0193) ... What the TypeScript SDK's stdio loop does, in Go: an empty name serves as MESH_SERVED_MODULE; each call runs beside the loop so a tool waiting on the runtime does not deadlock it; Emit asks the runtime (mesh/publish) with the same envelope and headers. README says how to install it and how releases are tagged.	2026-10-03 22:24:16 +02:00