clarify the current state of the DiskFile API
Change-Id: Ia3d62c53d14c9a5efdb9a39b08817320cf331085
This commit is contained in:
parent
55dafa2f07
commit
038878b1a4
@ -44,8 +44,9 @@ swift (1.11.0)
|
||||
The DiskFile abstraction for talking to data on disk has been
|
||||
refactored to allow alternate implementations to be developed.
|
||||
Included in the codebase is an in-memory reference
|
||||
implementation. For full documentation, please see
|
||||
http://docs.openstack.org/developer/swift/development_ondisk_backends.html
|
||||
implementation. For full documentation, please see the developer
|
||||
documentation. The DiskFile API is still a work in progress and
|
||||
is not yet finalized.
|
||||
|
||||
* Removal of swift-bench
|
||||
|
||||
|
@ -15,6 +15,8 @@ servers. For historical reasons, the object server backend reference
|
||||
implementation module is named `diskfile`, while the account and container
|
||||
server backend reference implementation modules are named appropriately.
|
||||
|
||||
This API is still under development and not yet finalized.
|
||||
|
||||
-----------------------------------------
|
||||
Back-end API for Account Server REST APIs
|
||||
-----------------------------------------
|
||||
|
Loading…
Reference in New Issue
Block a user