[keyple-dev] Keyple Distributed optimizations!

[Andrei Cristea <andrei.cristea019@xxxxxxxxx>]

Dear Keyple Community Members,

Two major optimizations of the Keyple Distributed solution aimed at reducing the number of network exchanges were released on September 06, 2024, one for the Reader Client Side mode and the other for the Reader Server Side mode.

Reader Client Side

The flag indicating whether the reader is contactless is now determined as soon as the reader is registered. It is cached and transmitted by the client to the server when the remote service is requested. This reduces the number of network exchanges, as the client no longer receives commands from the server requesting this information. The Server Json API has also been updated from version 2.0 to version 2.1.

Here is the list of the concerned components:

• Service
• Distributed Network
• Distributed Remote
• Distributed Local

Reader Server Side

When Reader Server Side is used in conjunction with pool plugins and the card resource service, it is possible to save up to 3 network exchanges per transaction. For this optimization to be effective, the following architecture must be implemented:

Here is the list of the concerned components:

• Service Resource
• Calypso Legacy SAM
• Generic

Best Regards

The Keyple Team