Community
Participate
Working Groups
In the scope of general API revision StreamCodec-related interfaces and implementations are to be also questioned against new API approach guides, revised and, most probably, reimplemented. As the result - new interfaces and implementation must appear complying with the new API approach. Functionality must be kept. - old ones are to be deprecated - tests should appear where possible
PR#1 https://github.com/eclipse-passage/passage/pull/275 - invite NamedData-based coverage for public string literals (encryption algorithm and key size) PR#2 https://github.com/eclipse-passage/passage/pull/277 - redesign StreamCodec and registry interfaces - rework existing BcStreamCodec implementation - deprecate it - plug the new one to Demo Framework
PR#3 https://github.com/eclipse-passage/passage/pull/278 - exhaustively test key pair generation - fix BcStreamCodec according to the test expectation PR#4 https://github.com/eclipse-passage/passage/pull/279 - test encoding for new BcStreamCodec PR#5 https://github.com/eclipse-passage/passage/pull/280 - test decoding for new BcStreamCodec
`lic.api` / `lic.internal.api.io` - general interfaces for codec, registry and all the required configurational constructions, documented `lic.base` / `lic.internal.base.io` - basic implementations for satellite structures `lic.bc` / `lic.internal.bc` - reimpementation for BouncyCastle-based stream coding and decoding for contemporary interfaces `lic.bc.tests` / `lic.internal.bc.tests` - tests set to be used as a cookbook, contract description and as documentation.