"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]
- native_state troubles John Keiser
- RE: multi-VMs (was re: native_state troubles) Paul Fisher
- RE: multi-VMs (was re: native_state troubles) John Keiser
- Re: multi-VMs (was re: native_state troubles) Paul Fisher
- Re: multi-VMs (was re: native_state troub... toshok
- RE: multi-VMs (was re: native_state ... John Keiser
- Re: multi-VMs (was re: native_state ... Paul Fisher
- Re: multi-VMs (was re: native_st... Bernd Kreimeier
- RE: multi-VMs (was re: native_state troub... John Keiser
- Re: multi-VMs (was re: native_state ... toshok
- Re: multi-VMs (was re: native_st... Bernd Kreimeier
- RE: multi-VMs (was re: native_st... John Keiser

