isn't tag field for this intended?
so if Twalk succeeded and Topen failed, souldn't the client be able to
track the failure of Topen based on tag?
in intro(5) it says:
" Each T-message has a tag field, chosen and used by the
client to identify the message. The reply to the message
will have the same tag. Clients must arrange that no two
outstanding messages on the same connection have the same
tag."
so this means to me that a client can send some T-messages and then
(or concurrently) wait the R-messages.
in inferno from mount(1) and styxmon(8) i deduced that this case is
also considered.
it's true that most of the servers i seen until now doesn't take
advantage of this feature, they respond to each T-message before
processing next message.
Dorin
2010/10/15 Latchesar Ionkov <[email protected]>:
> It can't be dealt with the current protocol. It doesn't guarantee that
> Topen will be executed once Twalk is done. So can get Rerrors even if
> Twalk succeeds.
>
> 2010/10/13 Venkatesh Srinivas <[email protected]>:
>>> 2) you can't pipeline requests if the result of one request depends on the
>>> result of a previous. for instance: walk to file, open it, read it, close
>>> it.
>>> if the first operation fails, then subsequent operations will be invalid.
>>
>> Given careful allocation of FIDs by a client, that can be dealt with -
>> operations on an invalid FID just get RErrors.
>>
>> -- vs
>>
>
>
