Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are two JavaSpaces implementations of any note: <a href="http://www.dancres.org/blitz/" rel="nofollow">Blitz</a> and <a href="http://gigaspaces.com" rel="nofollow">GigaSpaces XAP</a>. Blitz is open source; XAP is commercial, but has a community edition that's free for use.</p> <p>I'm heavily biased towards XAP; I work for them. :) That said, there are a lot of reasons to consider XAP:</p> <h2>Space Aquisition</h2> <p>The mechanism for acquiring a space reference is <strong>far</strong> easier with GigaSpaces than it is with default JINI:</p> <p>UrlSpaceConfigurer urlSpaceConfigurer = new UrlSpaceConfigurer("/./space"); IJSpace space = urlSpaceConfigurer.space(); // space is a close JavaSpaces analog, extended because the specification is rather limited</p> <p>GigaSpace gigaSpace=new GigaSpaceConfigurer(space).gigaSpace();</p> <p>// gigaSpace has <strong>many</strong> API improvements and is far more flexible.</p> <h2>API Improvements</h2> <p>The default JavaSpace API has no compensation for multiple tuple matches in the space. The more recent (i.e., 8 years old?) does, and Blitz implements it, but it's still not very flexible. Plus, you still get stuck with JINI Entries, which follow something like these rules:</p> <ol> <li>Every field must be public. (i.e., "public String foo")</li> <li>Every type must extend Entry.</li> <li>Every field must extend Object. (i.e., Long instead of long, etc.)</li> </ol> <p>XAP allows you to use Entry, but doesn't require it; with XAP, you can use ordinary POJOs. You still want to prefer Object types, because of wildcards (null is the JavaSpaces wildcard) but that's up to you.</p> <p>XAP also provides a SQL query mechanism, as well as a document-based model (schemaless) for entries, and can also use Spring to manage notifications and remoting.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload