I was playing around with sharing plumber between different machines
and found something I don't understand in the default 'basic' plumber
ruleset as it relates to 'page'.  Relevant excerpt from
/sys/lib/plumb/basic follows:

# image files go to page
type is text
data matches '[a-zA-Z¡-￿0-9_\-.,/]+'
data matches '([a-zA-Z¡-￿0-9_\-.,/]+)\.(jpe?g|JPE?G|gif|GIF|tiff?|TIFF?|ppm|PPM|bit|BIT|png|PNG|pgm|PGM|bmp|BMP|yuv|YUV)'
arg isfile	$0
plumb to image
plumb client page -wi

# page bookmarks
type is text
data matches '(([a-zA-Z¡-￿0-9_\-.,/]+)\.(ps|PS|eps|EPS|pdf|PDF|dvi|DVI|doc|DOC|epub|EPUB|cb[tz]|CB[TZ]))!(.+)'
arg isfile	$1
data set	$file
attr add	addr=$4
plumb to image
plumb start page -wij $0 $file

# postscript/pdf/dvi/doc go to page but not over the a plumb port
# the port is here for reference but is unused
type is text
data matches '[a-zA-Z¡-￿0-9_\-.,/]+'
data matches '([a-zA-Z¡-￿0-9_\-.,/]+)\.(ps|PS|eps|EPS|pdf|PDF|dvi|DVI|doc|DOC|epub|EPUB|cb[tz]|CB[TZ])'
arg isfile	$0
plumb to postscript
plumb start page -w $file

My question is, why do we send image files to a running page over the
plumb port, but not ps/pdf type files?  We send page bookmarks to
running page via the plumb port, but not standard files.  It is clear
from the comments that this is a delibrate decision, is there a good
reason for it?  From my perspective, the "plumb to postscript" in the
final ruleset shown here should be "plumb to image" to make all the
behavior consistent.

It's obviously a trivial point and easy to change if you want to, but
if there isn't a justification for this divergence in behavior,
perhaps we should just standardize it?

-mycroftiv