opendal 0.1.8 → 0.1.9

data/core/NOTICE

@@ -0,0 +1,5 @@
+Apache OpenDAL
+Copyright 2023-2026 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).

data/core/README.md

@@ -20,8 +20,8 @@ Apache OpenDAL™ is an Open Data Access Layer that enables seamless interaction
 - **API reference**: [docs.rs/opendal](https://docs.rs/opendal/) (release) | [dev](https://opendal.apache.org/docs/rust/opendal/)
 - **Services & configuration**: [opendal.apache.org/services](https://opendal.apache.org/services)
 - **Concepts**: [opendal.apache.org/docs/concepts](https://opendal.apache.org/docs/concepts)
-- [Upgrade Guide](https://docs.rs/opendal/latest/opendal/docs/upgrade/index.html) | [Release Notes](https://docs.rs/opendal/latest/opendal/docs/changelog/index.html) | [RFCs](https://docs.rs/opendal/latest/opendal/docs/rfcs/index.html)
-- [Examples](./examples)
+- [Upgrade Guide](https://github.com/apache/opendal/blob/main/core/core/src/docs/upgrade.md) | [Release Notes](https://github.com/apache/opendal/blob/main/CHANGELOG.md) | [RFCs](https://github.com/apache/opendal/tree/main/core/core/src/docs/rfcs)
+- [Examples](https://github.com/apache/opendal/tree/main/core/examples)
 
 ## Installation
 
@@ -83,8 +83,13 @@ timeout, and concurrency limit are built in:
 
 ```rust
 use opendal::layers::RetryLayer;
+use opendal::services::Memory;
+use opendal::{Operator, Result};
 
-let op = op.layer(RetryLayer::new());
+fn build_operator() -> Result<Operator> {
+    let op = Operator::new(Memory::default())?;
+    Ok(op.layer(RetryLayer::new()))
+}
 ```
 
 See [Going to production](https://opendal.apache.org/docs/core/production) and the
@@ -92,12 +97,12 @@ See [Going to production](https://opendal.apache.org/docs/core/production) and t
 
 ## Contributing
 
-Check out the [CONTRIBUTING](./CONTRIBUTING.md) guide for building, testing, and
+Check out the [CONTRIBUTING](https://github.com/apache/opendal/blob/main/CONTRIBUTING.md) guide for building, testing, and
 submitting changes to the core.
 
 ## Used by
 
-Check out the [users](./users.md) list for more details on who is using OpenDAL.
+Check out the [users](https://github.com/apache/opendal/blob/main/core/users.md) list for more details on who is using OpenDAL.
 
 ## Branding
 
@@ -107,6 +112,6 @@ For more details, see the [Apache Product Name Usage Guide](https://www.apache.o
 
 ## License and Trademarks
 
-Licensed under the Apache License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0
+Licensed under the Apache License, Version 2.0: <http://www.apache.org/licenses/LICENSE-2.0>
 
 Apache OpenDAL, OpenDAL, and Apache are either registered trademarks or trademarks of the Apache Software Foundation.

data/core/benches/vs_fs/Cargo.toml

@@ -22,7 +22,7 @@ license = "Apache-2.0"
 name = "opendal-benchmark-vs-fs"
 publish = false
 rust-version = "1.86"
-version = "0.58.0"
+version = "0.58.1"
 
 [dependencies]
 criterion = { version = "0.8.2", features = ["async", "async_tokio"] }

data/core/benches/vs_s3/Cargo.toml

@@ -22,7 +22,7 @@ license = "Apache-2.0"
 name = "opendal-benchmark-vs-s3"
 publish = false
 rust-version = "1.86"
-version = "0.58.0"
+version = "0.58.1"
 
 [dependencies]
 aws-config = { version = "1.0.1", features = ["behavior-version-latest"] }

data/core/core/Cargo.toml

@@ -21,6 +21,7 @@ description = "Apache OpenDAL™: One Layer, All Storage."
 exclude = ["/tests/"]
 keywords = ["storage", "fs", "s3", "azblob", "gcs"]
 name = "opendal-core"
+readme = "README.md"
 
 authors = { workspace = true }
 edition = { workspace = true }
@@ -61,7 +62,6 @@ services-memory = []
 
 [lib]
 bench = false
-doctest = false
 
 [dependencies]
 # Required dependencies
@@ -76,7 +76,7 @@ md-5 = "0.11.0"
 mea = { workspace = true }
 percent-encoding = "2"
 quick-xml = { workspace = true, features = ["serialize", "overlapped-lists"] }
-reqsign-core = { version = "3.0.1", default-features = false, optional = true }
+reqsign-core = { version = "3.2.0", default-features = false, optional = true }
 serde = { workspace = true, features = ["derive"] }
 serde_json = { workspace = true }
 tokio = { workspace = true, features = ["macros", "io-util"] }

data/core/core/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/core/core/NOTICE

@@ -0,0 +1,5 @@
+Apache OpenDAL
+Copyright 2023-2026 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).

data/core/core/README.md

@@ -0,0 +1,93 @@
+# Apache OpenDAL™ Core
+
+`opendal-core` contains the storage abstraction, operator APIs, extension
+traits, and shared infrastructure used by Apache OpenDAL™.
+
+Most applications should depend on the [`opendal`](https://crates.io/crates/opendal)
+facade. The facade re-exports the core APIs and wires optional service, layer,
+executor, and HTTP transport crates behind feature flags.
+
+Depend on `opendal-core` directly when implementing an OpenDAL service or layer,
+building a minimal integration from the split crates, or managing service
+registration and HTTP transport explicitly.
+
+## Quick start
+
+The in-memory service is always available:
+
+```shell
+cargo add opendal-core
+```
+
+```rust
+use opendal_core::services;
+use opendal_core::Operator;
+use opendal_core::Result;
+
+fn build_operator() -> Result<Operator> {
+    Operator::new(services::Memory::default())
+}
+```
+
+Storage services and optional layers live in separate
+`opendal-service-*` and `opendal-layer-*` crates. Applications using the facade
+can enable them through `services-*` and `layers-*` features instead.
+
+## Compose split crates
+
+Applications that depend on `opendal-core` directly compose storage and runtime
+behavior explicitly:
+
+- A service crate exports a builder that implements `opendal_core::Builder`.
+  Pass the configured builder to `Operator::new`.
+- A layer crate exports a type that implements `opendal_core::raw::Layer`. Pass
+  the configured layer to `Operator::layer`.
+- An HTTP transport crate exports an `opendal_core::HttpTransport`
+  implementation. Wrap it in `HttpTransporter` and place it in the operator's
+  `OperationContext`.
+
+For example, the following dependencies compose S3, retry, and the reqwest HTTP
+transport without the `opendal` facade:
+
+```shell
+cargo add opendal-core opendal-service-s3 opendal-layer-retry
+cargo add opendal-http-transport-reqwest
+```
+
+```rust,ignore
+use opendal_core::HttpTransporter;
+use opendal_core::OperationContext;
+use opendal_core::Operator;
+use opendal_core::Result;
+use opendal_http_transport_reqwest::ReqwestTransport;
+use opendal_layer_retry::RetryLayer;
+use opendal_service_s3::S3;
+
+fn build_operator(builder: S3) -> Result<Operator> {
+    let context = OperationContext::new()
+        .with_http_transport(HttpTransporter::new(ReqwestTransport::default()));
+
+    Ok(Operator::new(builder)?
+        .with_context(context)
+        .layer(RetryLayer::default()))
+}
+```
+
+Configure `builder` for the target S3-compatible service before passing it to
+`build_operator`.
+
+`Operator::new` uses the builder directly and does not require service
+registration. Call the service crate's `register_*_service` function with
+`OperatorRegistry::get()` only when using scheme-driven construction through
+`Operator::from_uri` or `Operator::via_iter`.
+
+## Documentation
+
+- [Rust API documentation](https://docs.rs/opendal-core)
+- [Apache OpenDAL Rust guide](https://opendal.apache.org/docs/core)
+- [Services and configuration](https://opendal.apache.org/services)
+- [Apache OpenDAL project](https://opendal.apache.org/)
+
+## License
+
+Licensed under the Apache License, Version 2.0.

data/core/core/src/blocking/delete.rs

@@ -40,7 +40,7 @@ impl Deleter {
     ///
     /// Also see:
     ///
-    /// - [`BlockingDeleter::delete_try_iter`]: delete an fallible iterator of paths.
+    /// - [`Deleter::delete_try_iter`]: delete a fallible iterator of paths.
     pub fn delete_iter<I, D>(&mut self, iter: I) -> Result<()>
     where
         I: IntoIterator<Item = D>,
@@ -53,7 +53,7 @@ impl Deleter {
     ///
     /// Also see:
     ///
-    /// - [`BlockingDeleter::delete_iter`]: delete an infallible iterator of paths.
+    /// - [`Deleter::delete_iter`]: delete an infallible iterator of paths.
     pub fn delete_try_iter<I, D>(&mut self, try_iter: I) -> Result<()>
     where
         I: IntoIterator<Item = Result<D>>,

data/core/core/src/blocking/list.rs

@@ -23,7 +23,8 @@ use crate::*;
 /// BlockingLister is designed to list entries at given path in a blocking
 /// manner.
 ///
-/// Users can construct Lister by [`blocking::Operator::lister`] or [`blocking::Operator::lister_with`].
+/// Users can construct a lister through [`Operator::lister`][crate::blocking::Operator::lister]
+/// or [`Operator::lister_options`][crate::blocking::Operator::lister_options].
 ///
 /// - Lister implements `Iterator<Item = Result<Entry>>`.
 /// - Lister will return `None` if there is no more entries or error has been returned.

data/core/core/src/blocking/operator.rs

@@ -282,7 +282,8 @@ impl Operator {
     /// | stat file with `/`     | `abc/def_file/` | Error `NotFound`                           |
     /// | stat not existing path | `xyz`           | Error `NotFound`                           |
     ///
-    /// Refer to [RFC: List Prefix][crate::docs::rfcs::rfc_3243_list_prefix] for more details.
+    /// Refer to [RFC: List Prefix](https://github.com/apache/opendal/blob/main/core/core/src/docs/rfcs/3243_list_prefix.md)
+    /// for more details.
     ///
     /// ## Services that not support `create_dir`
     ///
@@ -334,7 +335,8 @@ impl Operator {
     /// | stat file with `/`     | `abc/def_file/` | Error `NotFound`                           |
     /// | stat not existing path | `xyz`           | Error `NotFound`                           |
     ///
-    /// Refer to [RFC: List Prefix][crate::docs::rfcs::rfc_3243_list_prefix] for more details.
+    /// Refer to [RFC: List Prefix](https://github.com/apache/opendal/blob/main/core/core/src/docs/rfcs/3243_list_prefix.md)
+    /// for more details.
     ///
     /// ## Services that not support `create_dir`
     ///
@@ -711,11 +713,13 @@ impl Operator {
         self.handle.block_on(self.op.delete_try_iter(try_iter))
     }
 
-    /// Create a [`BlockingDeleter`] to continuously remove content from storage.
+    /// Create a [`blocking::Deleter`] to continuously remove content from
+    /// storage.
     ///
     /// It leverages batch deletion capabilities provided by storage services for efficient removal.
     ///
-    /// Users can have more control over the deletion process by using [`BlockingDeleter`] directly.
+    /// Use [`blocking::Deleter`] directly for more control over the deletion
+    /// process.
     pub fn deleter(&self) -> Result<blocking::Deleter> {
         blocking::Deleter::create(
             self.handle.clone(),
@@ -839,7 +843,8 @@ impl Operator {
 
     /// Create a streaming lister for entries whose paths start with the given prefix `path`.
     ///
-    /// This function creates a new [`BlockingLister`]; dropping it stops listing.
+    /// This function creates a new [`blocking::Lister`]; dropping it stops
+    /// listing.
     ///
     /// # Semantics
     ///

data/core/core/src/blocking/read/std_bytes_iterator.rs

@@ -22,7 +22,8 @@ use futures::StreamExt;
 
 use crate::*;
 
-/// StdIterator is the adapter of [`Iterator`] for [`BlockingReader`][crate::BlockingReader].
+/// `StdBytesIterator` adapts a [`crate::blocking::Reader`] into an
+/// [`Iterator`].
 ///
 /// Users can use this adapter in cases where they need to use [`Iterator`] trait.
 ///

data/core/core/src/blocking/read/std_reader.rs

@@ -27,7 +27,8 @@ use futures::AsyncSeekExt;
 
 use crate::*;
 
-/// StdReader is the adapter of [`Read`], [`Seek`] and [`BufRead`] for [`BlockingReader`][crate::BlockingReader].
+/// `StdReader` adapts a [`crate::blocking::Reader`] to [`Read`], [`Seek`], and
+/// [`BufRead`].
 ///
 /// Users can use this adapter in cases where they need to use [`Read`] or [`BufRead`] trait.
 ///

data/core/core/src/blocking/write/std_writer.rs

@@ -21,7 +21,7 @@ use futures::AsyncWriteExt;
 
 use crate::*;
 
-/// StdWriter is the adapter of [`std::io::Write`] for [`BlockingWriter`].
+/// `StdWriter` adapts a [`crate::blocking::Writer`] to [`std::io::Write`].
 ///
 /// Users can use this adapter in cases where they need to use [`std::io::Write`] related trait.
 ///

data/core/core/src/docs/performance/http_optimization.md

@@ -1,6 +1,14 @@
 # HTTP Optimization
 
-All OpenDAL HTTP-based storage services use the same [HttpTransporter][crate::HttpTransporter] abstraction. This design offers users a unified interface for configuring HTTP transports. The `opendal` facade installs [reqwest](https://crates.io/crates/reqwest) as the default HTTP transport when the `http-transport-reqwest` feature is enabled.
+All OpenDAL HTTP-based storage services use the same
+[HttpTransporter][crate::HttpTransporter] abstraction. This design offers users
+a unified interface for configuring HTTP transports. The `opendal` facade
+installs [reqwest](https://crates.io/crates/reqwest) as the default HTTP transport
+when `opendal::install_default()` is called with the `http-transport-reqwest`
+feature enabled. The default `auto-register-services` feature calls
+`install_default()` before `main`. Applications that need to install their own
+process-wide transport should disable `auto-register-services`; transports
+configured directly on an operator are unaffected.
 
 Many of the services supported by OpenDAL are HTTP-based. This guide aims to provide optimization tips for using HTTP-based storage services. While these tips are also applicable to other HTTP clients, the configuration methods may vary.
 

data/core/core/src/docs/rfcs/7749_http_transporter.md

@@ -182,9 +182,12 @@ transport with `HttpTransporter::install_default(...)` or configure an operator
 with `.http_transport(...)`.
 
 `HttpTransporter::install_default` is first-wins, returns no error, and does not
-overwrite an already installed default. Users that need process-wide replacement
-must install before the facade default is installed; otherwise they should use
-operator-level `.http_transport(...)`.
+overwrite an already installed default. The facade installs its default before
+`main` when `auto-register-services` is enabled. Users that need process-wide
+replacement must disable `auto-register-services`, install their transport
+themselves, and call `init_default_registry()` explicitly when URI-based
+construction is needed. Otherwise, they should use operator-level
+`.http_transport(...)`.
 
 The operator-registry-only public entry `init_default_registry()` remains for
 compatibility. It does not install HTTP transport. The facade
@@ -207,8 +210,9 @@ published artifact. Release tooling must publish the transport crate before the
 facade package that depends on it.
 
 The process-wide default transport remains global state. The design keeps it
-minimal and first-wins, but users that need strict control must install their
-default before facade auto-installation or configure transports per operator.
+minimal and first-wins, but users that need strict control must disable facade
+auto-installation and own default initialization or configure transports per
+operator.
 
 # Rationale and alternatives
 

data/core/core/src/layers/mod.rs

@@ -15,7 +15,12 @@
 // specific language governing permissions and limitations
 // under the License.
 
-//! `Layer` is the mechanism to intercept operations.
+//! Core layers used by `opendal-core`.
+//!
+//! A [`crate::raw::Layer`] wraps an access implementation to intercept or adjust
+//! operations. Optional reusable layers such as retry, timeout, logging, and
+//! metrics live in `opendal-layer-*` crates and are re-exported by the
+//! `opendal` facade behind `layers-*` Cargo features.
 
 mod error_context;
 pub(crate) use error_context::ErrorContextLayer;