emboss/krypt-core — comment on commit e6d9b5db4f0dd78b4d6d95db40716545271afca2
File:  line 0
By emboss:

Thank you! Yeah, you're right about this - I was blocked in my thoughts... We can already discuss and specify the interfaces even without knowing how we would exactly realize an "engine/provider" concept. Thanks a lot, I will point to this when discussing the corresponding point from the proposal.

About the engine concept: I think I have something for Java, but I still struggle to find a good way for registering a provider from an additional library in C. In Java, we have static initializers where we could call "KryptCryptoProvider.addProvider(new ThisProvider());", but what would we do with a C library for krypt-core (C). There is no real equivalent to static initializers, or is there? Unfortunately, we don't have the convenience of a Init_xxx method like we have for Ruby extensions, this would be just a regular .so that we link against. What could we use as an entry point during initialization there?