From b2d061d66c860ad763da72f3cd4b87ce2f53c248 Mon Sep 17 00:00:00 2001 From: Heiko Schaefer Date: Wed, 23 Mar 2022 12:10:38 +0100 Subject: [PATCH] Update high level documentation on backends --- README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c0ab32e..e4039b7 100644 --- a/README.md +++ b/README.md @@ -65,6 +65,7 @@ implementation. Typically, `openpgp-card` will be used with the `openpgp-card-pcsc` backend, which uses the standard pcsclite library to communicate with cards. + However, alternative backends can be used and may be useful. The experimental, alternative `openpgp-card-scdc` backend uses scdaemon from the GnuPG project as a low-level transport layer to interact with OpenPGP @@ -73,9 +74,11 @@ cards. Backends implement: 1) functionality to find and connect to a card (these operations may vary - significantly between different backends), and + significantly between different backends), -2) a very simple communication primitive, by implementing the `CardClient` +2) transaction management (where applicable), by implementing the `CardBackend` trait, and + +3) simple communication primitives, by implementing the `CardTransaction` trait, to send individual APDU commands and receive responses. All higher level and/or OpenPGP card-specific logic (including command