commflow
  • English

      • Capability Status

      This page compares exports in commflow@0.0.2 with the four communication families in the planned product guide, so you can tell which code runs today.

      How To Read This Map

      Use this page to understand the product direction, not as a list of runtime APIs already available in commflow@0.0.2.

      Current Vs Complete Contract

      FamilyCurrent 0.0.2 statePlanned contractUse it today?
      requestManifest metadata onlyOne-shot request/response orchestration with timeout, retry, trace, proxy, and hooksUse metadata only. Do not import a request client yet.
      sseManifest metadata onlyServer-to-client event streamsUse metadata only. Runtime support is not released.
      rpcManifest metadata onlyProcedure-style communication with typed contractsUse metadata only. Runtime support is not released.
      socketManifest metadata onlyLong-lived duplex messagingUse metadata only. Runtime support is not released.

      If you need field-level details for the metadata itself, read Manifest API.

      Request

      The complete request contract targets one-shot request/response flows and covers:

      • timeout control
      • retry policy
      • trace metadata propagation
      • proxy selection
      • lifecycle hooks

      SSE

      sse provides server-to-client one-way delivery. It is useful when a service needs to push ordered events without a bidirectional socket.

      RPC

      rpc provides procedure-style communication focused on typed contracts and transport adapters.

      Socket

      socket provides long-lived duplex messaging for event-driven coordination, session-aware messages, and realtime flows.

      Current Release Boundary

      commflow@0.0.2 only exposes channel metadata. Run current code from Current Release Quick Start; read Request, SSE, RPC, and Socket for planned workflows.