foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-11-24 15:19:26 -05:00
Code Issues Packages 1 Wiki Activity
denoland-deno/ext/kv
History
Yusuke Tanaka 0e2f6e38e7
feat(ext/fetch): Make fetch client parameters configurable (#26909) 
This commit makes HTTP client parameters used in `fetch` API
configurable on the extension initialization via a callback
`client_builder_hook` that users can provide.

The main motivation behind this change is to allow `deno_fetch` users to
tune the HTTP/2 client to suit their needs, although Deno CLI users will
not benefit from it as no JavaScript interface is exposed to set these
parameters currently.

It is up to users whether to provide a hook function. If not provided,
the default configuration from hyper crate will be used.

Ref #26785
2024-11-18 17:48:57 -08:00
..
01_db.ts refactor(ext/kv): align error messages (#25500) 2024-09-19 13:20:09 +05:30
Cargo.toml refactor: use boxed_error in some places (#26887) 2024-11-15 23:22:50 -05:00
config.rs chore: make fields public on PermissionDeniedError and deno_kv::KvConfig (#26798) 2024-11-12 17:49:49 +00:00
dynamic.rs chore: update copyright to 2024 (#21753) 2024-01-01 19:58:21 +00:00
interface.rs chore: update copyright to 2024 (#21753) 2024-01-01 19:58:21 +00:00
lib.rs refactor: use boxed_error in some places (#26887) 2024-11-15 23:22:50 -05:00
README.md fix(docs): fix some deno.land/manual broken urls (#24557) 2024-07-15 11:08:45 +00:00
remote.rs feat(ext/fetch): Make fetch client parameters configurable (#26909) 2024-11-18 17:48:57 -08:00
sqlite.rs refactor(runtime/permissions): use concrete error types (#26464) 2024-11-04 09:17:21 -08:00

README.md

deno_kv

This crate provides a key/value store for Deno. For an overview of Deno KV, please read the manual.

Storage Backends

Deno KV has a pluggable storage interface that supports multiple backends:

  • SQLite - backed by a local SQLite database. This backend is suitable for development and is the default when running locally. It is implemented in the denokv_sqlite crate.
  • Remote - backed by a remote service that implements the KV Connect protocol, for example Deno Deploy.

Additional backends can be added by implementing the Database trait.

KV Connect

The KV Connect protocol allows the Deno CLI to communicate with a remote KV database. The specification for the protocol, and the protobuf definitions can be found in the denokv repository, under the proto directory.