Project

General

Profile

Feature #181

Remove Threading from GUI Executor

Added by Tobias Wich about 6 years ago. Updated 7 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
Start date:
03/13/2013
Due date:
% Done:

0%

Reviewer:
Build Version:

Description

Card transactions limit the issuing of APDUs to the current thread. At the moment, the executer runs actions in a seperate thread, so that it can abort the action. This behaviour prevents us from using transactions in a majority of use cases (e.g. EAC).

To resolve this issue, rewrite the executor to run actions in the same thread while keeping the possibility to cancel running actions.

It is also worth investingating whether actions really need to be cancellable. The action threading was introduced, because there was no possibility to cancel a running PACE call issued to a standard or comfort reader. Maybe it is acceptable to not cancel actions and rely on the user to do this on the reader itself.


Related issues

Related to Feature #166: Cancel support for long running PCSC commands New 01/18/2013
Related to Bug #215: Card Recognition with Transactions Closed 04/08/2013

History

#1 Updated by Tobias Wich almost 5 years ago

  • Target version changed from 1.1.0 to 1.3.0

#2 Updated by Tobias Wich over 3 years ago

  • Tracker changed from Bug to Feature

#3 Updated by Tobias Wich 7 months ago

  • Status changed from New to Closed

Fixed by having all card related actions in one thread of the application.

Also available in: Atom PDF