{'fraction_non_alphanumeric': 0.017711171662125342, 'fraction_numerical': 0.005449591280653951, 'mean_word_length': 5.447368421052632, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Transactions in Java Card

A smart-card run-time environment must provide proper transaction support for the reliable updating of data, especially on multi-application cards like the Java Card. The transaction mechanism must meet these demands by means of the applications and the system itself, within the minimal resources offered by current smart-card hardware. This paper presents the current transaction model implied by the Java Card 2.1 specification, highlights its shortcomings and presents a detailed discussion of possible implementation schemes and their optimizations. It especially addresses the problem of object instantiations within a transaction in the Java Card 2.1 specification and presents an effective solution.