Skip to content

Commit

Permalink
fix css
Browse files Browse the repository at this point in the history
  • Loading branch information
pterr committed Nov 20, 2024
1 parent e74089e commit 728aab2
Showing 1 changed file with 7 additions and 4 deletions.
11 changes: 7 additions & 4 deletions content/keyple-support/reader-plugins/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,14 +15,14 @@ In general, all “contactless” reader solutions are observable, because for t
On the other hand, for some “contact” reader solutions, card presence is statically defined: these readers don't need to be observed.

## Properties of a smartcard reader solution through the Keyple Service API
For a Keyple-based terminal, smartcard reader solutions are interfaced using reader plug-ins. Keyple's Service API enables ticket terminal applications to access “locally” 3 categories of reader solutions:
For a Keyple-based terminal, smartcard reader solutions are interfaced using reader plug-ins. Keyple's Service API enables ticketing terminal applications to access “locally” 3 categories of reader solutions:
- a “simple” plugin enables only static configuration of smartcard readers → the most common case in embedded systems.
- an “observable” plugin enables the management of reader solutions that can be hot-plugged or hot-disconnected. → mainly 2 uses: readers connected over serial links (e.g. USB), or mobile solutions with an energy-saving mode (reader power supply cut off at standby).
- a “pool” plugin for interfacing with solutions offering dynamic allocation of reader resources according to the need. → this is how an HSM-type solution works.

## Integrating a smartcard reader solution into Keyple through the Plugin API
For a Keyple-based terminal, a dedicated plug-in for any smart card reader solution must implement Keyple's Plugin API:
- SPIs are differentiated for the 2 reader types and the 3 plug-in categories in particular
- SPIs are differentiated in particular for the 2 reader types and the 3 plug-in categories.
- other features are linked to the native API capabilities of reader solutions:
- autonomy to manage the Select Application command
- autonomous synchronous, autonomous asynchronous or non-autonomous card insertion detection,
Expand Down Expand Up @@ -102,6 +102,9 @@ document.body.onload = function() {
</script>

<style>
.rotated {
writing-mode: sideways-lr;
}
.hachured {
background-image: repeating-linear-gradient(
45deg,
Expand All @@ -126,7 +129,7 @@ document.body.onload = function() {
</thead>
<tbody>
<tr>
<th scope="rowgroup" rowspan="4">plugin</th>
<th scope="rowgroup" rowspan="4" class="rotated">plugin</th>
<td>PluginSpi</td>
<td>✓</td>
<td>✓</td>
Expand Down Expand Up @@ -159,7 +162,7 @@ document.body.onload = function() {
<td>✓</td>
</tr>
<tr>
<th scope="rowgroup" rowspan="4">contact</th>
<th scope="rowgroup" rowspan="4" class="rotated">contact</th>
<td>ReaderSpi</td>
<td>✓</td>
<td>✓</td>
Expand Down

0 comments on commit 728aab2

Please sign in to comment.