{"version":"2.1.280","anchor":"plugin-host-ops-gained-a-streaming-pullclose-protocol","canonical_anchor":"plugin-host-ops-gained-a-streaming-pullclose-protocol","heading":"Plugin host ops gained a streaming pull\/close protocol","tier":"internal","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/plugin-host-ops-gained-a-streaming-pullclose-protocol","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Plugin host ops gained a streaming pull\/close protocol\n\nPlugin hooks gained a streaming pull\/close protocol underlying features like process.spawn\n\n**What**\n\nThe worker process that runs plugin hooks now supports a streaming protocol for its internal operations, in addition to the simple request\/response calls it already had. This adds message types for pulling further data (`op_pull`) and closing a stream (`op_close`), along with supporting dispatch and context-building code.\n\n**Why**\n\nThis is the underlying plumbing that makes new streaming operations, such as `process.spawn`, possible: it lets a plugin operation send back a sequence of results over time instead of just a single reply.\n\n- Area: Plugins\n- Names: `op_pull`, `op_close`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}