I've been wondering the same. Extending the current capabilities only slightly, one could have a cascade of plumbers.
I think if plumber could create one more pre-defined (writable) file, let's call it 'pass', in addition to 'send' and 'rules', then a rule could choose to forward the request down stream (i.e. 'plumb to pass'). Using either the shell for plumbing or a new flag in plumber, an upstream's 'pass' file could be connected to (potentially multiple) downstream plumber 'send' file(s). On Thu, Jul 16, 2026 at 10:34 PM Devon H. O'Dell <[email protected]> wrote: > > ISTM the problem is that you want broadcast semantics for some things (e.g., > opening an image with page) and directed semantics for others (e.g., sending > a manpage to the acme that clicked). Would it be worth adding semantics to > caller and rules to allow a caller to specify it specifically is interested > in the result, and have rules that match if the caller specifies the desire? > > There are a lot of individual ways to solve the specific issue of manpages, > but they don't seem to work generally without this. > > --dho > ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tc15b39be3656afe0-M50a8e05f3d3fa4f2bdf5ebc2 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
