Task #2900
closed
Flatten FinalBlockId
0%
Description
Currently FinalBlockId is defined as a TLV that contains another name component TLV.
If there is no other purpose for it, FinalBlockId itself should be the name component TLV.
Updated by Junxiao Shi over 9 years ago
- Description updated (diff)
- Start date deleted (
06/14/2015)
One issue is: it's less expressive.
Compare these:
<MetaInfo> <MetaInfo>
<ContentType>BLOB</ContentType> <ContentType>BLOB</ContentType>
<FinalBlockId><NameComponent>%00%09</NameComponent></FinalBlockId> <NameComponent>%00%09</NameComponent>
</MetaInfo> </MetaInfo>
It's obscure what NameComponent means.
Updated by Tai-Lin Chu over 9 years ago
The example above should be
<FinalBlockId>%00%09</FinalBlockId>
Is there a reason why FinalBlockID is not a boolean besides the fact that one cannot specify it before the final block?
Updated by Junxiao Shi over 9 years ago
- Subject changed from Flatten FinalBlockID to Flatten FinalBlockId
- Description updated (diff)
<FinalBlockId>%00%09</FinalBlockId>
There are multiple name component types: generic NameComponent, ImplicitSha256DigestComponent, and MarkedComponent (#2012).
All types except ImplicitSha256DigestComponent can appear in FinalBlockId.
The proposed format is ambiguous because type is lost.
Is there a reason why FinalBlockID is not a boolean besides the fact that one cannot specify it before the final block?
FinalBlockId SHOULD appear in the last segment, and MAY appear in other segments to give consumer an early warning.
Updated by Tai-Lin Chu over 9 years ago
- Status changed from New to Resolved
We can close this if this is needed for typed components.
Updated by Junxiao Shi over 9 years ago
- Status changed from Resolved to Rejected