note possibility of using single protocol for both mutable and immutable files
[Imported from Trac: page NewCapDesign, version 15]
parent
db95a35852
commit
61688b336b
|
@ -6,9 +6,10 @@ across separate tickets: this page is here to consolidate them. We should not
|
||||||
release a new filecap format without checking it against everything on this
|
release a new filecap format without checking it against everything on this
|
||||||
list.
|
list.
|
||||||
|
|
||||||
There will be a related pair of new encoding designs. The
|
There will be a related pair of new encoding designs/protocols (or equivalent;
|
||||||
[NewImmutableEncodingDesign](NewImmutableEncodingDesign) and [NewMutableEncodingDesign](NewMutableEncodingDesign) pages will hold those
|
it has also been suggested that a single protocol could support both mutable and
|
||||||
design discussions.
|
immutable files). The [NewImmutableEncodingDesign](NewImmutableEncodingDesign) and [NewMutableEncodingDesign](NewMutableEncodingDesign)
|
||||||
|
pages will hold those design discussions.
|
||||||
|
|
||||||
Ticket #432 was the starting point: it contained a list of features.
|
Ticket #432 was the starting point: it contained a list of features.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue