[Isolate-interest] Shared-memory based JavaSpace between Isolates?

[Curt Cox]

What do you mean by "a shared-memory based JavaSpace" and what
would the advantages be?

Do you have a specific implementation strategy in mind?
Is there a type of problem or issue you are seeking to address?

Or are you just thinking aloud?

Long-time subscribers to this list will know that I do that often.

It seems to me that a JavaSpace is essentially a "shared-memory"
to begin with.  I'm not sure what the advantage would be of using
multiple isolates to implement a JavaSpace, only to couple them
using shared memory.

What sort of hardware would be the deployment target for such
a beast?

-Curt

-----Original Message-----
From: isolate-interest-admin@cs.oswego.edu
[mailto:isolate-interest-admin@cs.oswego.edu]On Behalf Of Bernhard
Fastenrath
Sent: Saturday, March 13, 2004 12:55 PM
To: isolate-interest@altair.cs.oswego.edu
Subject: [Isolate-interest] Shared-memory based JavaSpace between
Isolates?



Are there any plans to provide a shared-memory based
JavaSpace between different Isolates?

If not, is there a recommended procedure to implement
something like that, maybe using a native library?

Bernhard

_______________________________________________
Isolate-interest mailing list
Isolate-interest@altair.cs.oswego.edu
http://altair.cs.oswego.edu/mailman/listinfo/isolate-interest