There are several situations where a server needs to take two
different files, and they may not be a net.Conn, e.g. from a
pipe or stdin/stdout (both of these are occuring in the cpu
command).
This is pretty standard for 9p servers:
you can see it in the Linux 9p fs with its use
of rfdno and wfdno. Plan 9, similarly, allowed for use of
two different fds for servers.
Change the Handle and underlying transport code to use an
io.ReadCloser and io.WriteCloser for T and R messages
respectively.
This builds, but won't test yet:
client_test.go:21:2: cannot find package "github.com/hugelgupf/socketpair" in any of:
/home/rminnich/go/src/github.com/hugelgupf/socketpair (from $GOROOT)
/home/rminnich/gopath/src/github.com/hugelgupf/socketpair (from $GOPATH)
FAIL github.com/hugelgupf/p9/p9 [setup failed]
There are several situations where a server needs to take two different files, and they may not be a net.Conn, e.g. from a pipe or stdin/stdout (both of these are occuring in the cpu command).
This is pretty standard for 9p servers: you can see it in the Linux 9p fs with its use of rfdno and wfdno. Plan 9, similarly, allowed for use of two different fds for servers.
Change the Handle and underlying transport code to use an io.ReadCloser and io.WriteCloser for T and R messages respectively.
This builds, but won't test yet: client_test.go:21:2: cannot find package "github.com/hugelgupf/socketpair" in any of: /home/rminnich/go/src/github.com/hugelgupf/socketpair (from $GOROOT) /home/rminnich/gopath/src/github.com/hugelgupf/socketpair (from $GOPATH) FAIL github.com/hugelgupf/p9/p9 [setup failed]
Not sure of the correct way to fix this.
I need this for the cpu command.