[Isolate-interest] isolates and native libraries / shared memory

[Pete Soper]

Hi Bernard,

The specification is silent about non-Java interface contracts. Native
libraries, and especially their name space semantics, are platform dependent.
For example with Solaris it's possible to arrange separate namespaces for
multiple instances of the same .so file while on other platforms this is
impossible (but with the above Solaris circumstance Java doesn't support
the disambiguation needed to, for example, have the same native library
within the scope of two classloaders.

Tell us more to understand what you mean by "shared memory identifier between
isolates." 

Regards,
Pete

Bernhard Fastenrath <bfastenrath@mac.com> said:
> 
> If I want to create a native library for unix implementing JavaSpaces 
> between VMs or Isolates,
> what assumptions can I make about Isolates?
> 
> If one isolate loads a native library, will another isolate be able to 
> access the library?
> If I try to shared memory identifier between Isolates, is there a 
> situation where this
> might fail? (for example Isolates running on different cluster nodes or 
> similar concepts).
> 
> Bernhard
> 
> _______________________________________________
> Isolate-interest mailing list
> Isolate-interest@altair.cs.oswego.edu
> http://altair.cs.oswego.edu/mailman/listinfo/isolate-interest
> 
--
Pete