> The advantage I see with this method is that the same java code can be
> loaded on both JOS and other platforms; the only difference is in the
> *implementation* of the native parts. It's sort of like JNI for Java,
> instead of for C.
I had come to the conclusion that something like this would be
necessary, if only because we don't have the resources to maintain a
classpath fork large enough to have replaced all the relevant native code
calls. It's a good idea, and I hope the implementation will be relatively
simple, but alot of that depends on how complicated JNI is. (And how much
of JNI we actually have to implement, given that most of the calls will
reflect right back out to Java...)
Anyway, I'll stop wasting your time and get back to coding.
Thanks.
-_Quinn
