emboss/krypt-core-jruby — comment on commit 182ba4bf7e362a1365b09c93b345dff217369241
File:  line 0
By nahi:

For Parser, Header, Asn.1 interface including 'tagging', I don't have enough knowledge to comment now. I'm sorry I can comment that but let's keep as-is and see how it goes :)

For krypt library hierarchy, I understood your concern about bridges like krypt-core-c and krypt-core-java(!= jruby). And I don't want to decode something about bridge naming and design to refrain from YAGNI issue.

+ krypt (Ruby imlementation)
+ krypt-core API (just a spec)
+ krypt-core (Ruby C-ext for CRuby and Rubinius)
+ krypt-core-jruby (JRuby ext)

This is my new understanding of hierarchy and resources for 'krypt-core API' should be in krypt/spec/krypt-core and krypt/doc/krypt-core. And you'd define 'krypt-bridge API' later.

Is this right?