8000 Add callback to createNetwork() so one can wait for all components to be ready. by rybesh · Pull Request #29 · noflo/noflo · GitHub
[go: up one dir, main page]

Skip to content

Add callback to createNetwork() so one can wait for all components to be ready. - #29

Closed
rybesh wants to merge 1 commit into
noflo:masterfrom
rybesh:create-network-callback
Closed

rybesh wants to merge 1 commit into
noflo:masterfrom
rybesh:create-network-callback

Conversation

@rybesh
@rybesh rybesh commented May 23, 2012
Copy link
Copy Markdown
Contributor

No description provided.

@bergie
bergie commented Oct 1, 2012
Copy link
Copy Markdown
Member

@rybesh sorry about taking my time with these. This pull req doesn't apply cleanly any longer, unfortunately. Can you rebase and push so it gets updated?

This may also be somewhat related to #40

@bergie
bergie commented Nov 8, 2012
Copy link
Copy Markdown
Member

@rybesh there is an initial callback support there now with the new Component Loader from #49. I'll try to merge that with your PR

@bergie bergie closed this in 9bf7d3d Nov 9, 2012
AsherBond pushed a commit to AsherBond/noflo that referenced this pull request Oct 12, 2026
Add another option to configure the permissions.
AsherBond pushed a commit to AsherBond/noflo that referenced this pull request Oct 19, 2026
@noflo/runtime-client: the client side of FBP Protocol 2.0 over
Reticulum, seeded from the runtime's hand-rolled integration client
(work document noflo#29):

- discoverRuntime: the announce scanner (aspect-filtered, version-
  checked, name-pinnable)
- connectRuntime: Destination recall, link establishment, identify(),
  and the runtime's unilateral 0x02 auth response with the capability
  mask
- RuntimeClient: frame send/receive over the link, the registry
  Two-Step Cache client (syncRegistry), plane listing, the graph mirror
  (syncGraph: epoch handshake, stale-epoch baseline fetch via
  link.request, importFbpJson into a GraphModel), 0x14 op emission and
  re-emission as op events, and link teardown

Receive path arms before send (the reply may arrive in the same tick);
the fields/epoch config persists across activations. Codec d.ts synced
with the implementations (encodeCrdtSyncReq planeId, decodeCrdt*
returns), and the fbp-protocol index re-exports the plane listing.
Tests run over a fake link (recorded sends, injected frames, resource
map); the live-rnsd E2E stays opt-in via RUNTIME_E2E_RNSD.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0