I neglected to mention: I find the prospect of Sun supporting multiple VMs
in the same process, even in serial (not necessarily in parallel), to be
extremely unlikely. This is because all of their native code would have to
be updated and likely made slower (at least one simple if() check would have
to be added to every place where FindClass() is called, in the minimal case
I can come up with).
Therefore, it is unlikely that anyone will code native Java to work with
multiple VMs.
Unless they write code to work only on Japhar.
IMHO, we should use some sort of a macro library, like jnilink, to use
FindClass(). Then those macros can be updated to support multiple VMs if we
want.
--John Keiser
> -----Original Message-----
> From: Paul Fisher [mailto:[EMAIL PROTECTED]]On Behalf Of Paul Fisher
> Sent: Wednesday, August 19, 1998 11:59 AM
> To: Classpath
> Subject: Re: native_state troubles
>
>
> "John Keiser" <[EMAIL PROTECTED]> writes:
>
> > Jeez, multiple VMs are a friggin *nightmare* -- this whole class
> > caching issue is just one facet.
>
> native_state uses common practices that JavaSoft recommends for
> writing JNI code. If native_state doesn't work in a multi-VM
> environment, then the majority of JNI code out there will not.
>
> Does anyone know if JavaSoft is going to address this problem?
>
> --
> Paul Fisher * [EMAIL PROTECTED]
>
>
