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

>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.

About krypt-core-jruby vs. krypt-core-java: I actually prefer krypt-core-java now over krypt-core-jruby. Especially since after Milestone 1, I'd like to add a pure Ruby krypt-core-ruby to compare performance stats. krypt-core-c, -java and -ruby seem to express their intent better, don't you think? If you agree, I will rename krypt-core-jruby to krypt-core-java.

PS: I'll try 'jruby -S rake coverage' and let you know the outcome.

About the hierarchy: Yes, that's my current understanding now, too. krypt-core is just a spec, while there are several implementations in different programming languages. With this in mind, I'd like to rename the current krypt-core to krypt-core-c and krypt-core-jruby to krypt-core-java. I agree that we should postpone the definition of the "bridge" interfaces until after Milestone 1. They are not really required neither by ASN.1 nor Template, so we should take the time to design them carefully. I would assume that the integration issue (how to include the bridge .so/.dll or .jar) will require some experimenting :)
Also agreed that resources for krypt-core API (especially on the Ruby level such as tests, specs and benchmarks) should go to krypt/spec/krypt-core and krypt/doc/krypt-core.