David Leimbach a écrit :
Transactions are tagged right? So you can, in fact, have many in
flight at once.
Perhaps I'm missing what you meant by pipelined.
I meant sending a couple of requests on one fid before receiving
replies.
Yes transaction are tagged, this doesn't mean that requests are
serialized (processed in order).
See the example sent by Derek :
1 send: open,fid,file
2 send: read,fid,args
3 send: read,fid,args
(wait one rtt)
4 recv: open success/fail
5 recv: read result / read error due to unknown fid
7 recv: read result / read error due to unknown fid
I see no reason for the server to not reply the 2nd request
before the 1st one : by example the server can receive all
the requests and distpach those reqs to different tasks.
Because all transactions are tagged ... this wouldn't break
9P. However, this doesn't work as expected.
That's why I think 9P was not designed to allow this. But
maybe I'm wrong.
Phil;
