in spec, clarify that block format does not have to be a single flat file
This commit is contained in:
parent
bf2fe9d085
commit
5762e249bf
1 changed files with 5 additions and 1 deletions
6
spec.txt
6
spec.txt
|
@ -453,7 +453,7 @@ Writing a block:
|
||||||
|
|
||||||
# block file format
|
# block file format
|
||||||
|
|
||||||
An implementation of ilo is free to choose the best approach to
|
An implementation is free to choose the best approach to
|
||||||
implementing the actual block storage. For the reference model,
|
implementing the actual block storage. For the reference model,
|
||||||
a flat file is used, with each block being stored sequentially.
|
a flat file is used, with each block being stored sequentially.
|
||||||
|
|
||||||
|
@ -463,3 +463,7 @@ packing or unpacking from memory as needed.
|
||||||
|
|
||||||
As with the image, the block file in the reference model is
|
As with the image, the block file in the reference model is
|
||||||
stored in little endian format.
|
stored in little endian format.
|
||||||
|
|
||||||
|
This is not required. An implementation could store blocks as
|
||||||
|
individual files, using a database, or in whatever form the
|
||||||
|
implementor desires.
|
||||||
|
|
Loading…
Reference in a new issue