Peter Cai e48f9aa828 refactor: Channel validity, and reconnection ... * ApduInterfaces also need a concept of validity based on the underlying APDU channel. For example, OMAPI depends on SEService being still connected. * We then rely on this validity to wait for reconnection; we do not need to manually remove all channels under a slot because the rest will be invalid anyway, and the next attempt at connection will lazily recreate the channel. * We had to manage channels manually before during reconnect because `valid` may result in SIGSEGV's when the underlying APDU channel has become invalid. This is avoided by the validity concept added to APDU channels.		2024-03-22 21:08:59 -04:00
..
src	refactor: Channel validity, and reconnection	2024-03-22 21:08:59 -04:00
build.gradle.kts	lpac-jni: Use APP_LDFLAGS instead of cFlags in build.gradle	2024-01-12 21:29:35 -05:00
consumer-rules.pro
LICENSE	Relicense lpac-jni to LGPLv2 to match lpac	2024-02-18 13:52:48 -05:00
proguard-rules.pro