a |b |c |d |e |f |g |h |i |j |k |l |m |n |o |p |q |r |s |t |u |v |w |x |y |z |

XSTM

What is XSTM?


XSTM is a n open sourcelibrary which enables high performance object replication between processes. It is an object oriented Distributed Shared Memory, or a Distributed Object Cache.

XSTMhas similarities with technologies like Adobe Flex Data Services , JBoss Cache, Terracotta, Tangosol Coherence , ScaleOut , or IBM's ObjectGrid .

Our model is based on object shares, which work like file shares. When an object is added to a share, it appears on the other machines which have the same share opened. Modifications done to the fields of the object are from this point replicated between machines.

Read more in the project overview.


XSTMis made of three projects. The Java implementation is called JSTMand is the base from which the other versions are derived. An adapted version made with Luciano, the author of GWM , is available for GWT . It allowsthis library to be used in a browser. NSTM is a .NET port based on IKVM.

All implementations are compatible with each other so object replication can take place e.g. between a Java server and a .NET Smart Client.

Related javascript Articles


Spoiler Blocker When JS Isn’t Available


Ever gone to a site to read up on your favorite show or get the lowdown on a new movie only to have the whole plot spoiled because you weren't forewarned that the "whole freakin' script" was injected into the article?!?! Yeah, I've been there and it ain't fun!

Chris Coyier of CSS-Trickscame up with a solution called Fade-in Spoiler Revealer which used jQueryto allow the user to click on a div that blocked view of the spoiler and see the contents. This was a very cool technique and caught the attention of Brian Dillard. Brian wondered how this script could be adapted to work with RSS readers and mobile browsers:

My only reservation about Coyier's technique was its reliance on JavaScript, and only JavaScript, to hide spoiler-laden content. With RSS and mobile browsing on the rise, lots of people read content in user-agents without JavaScript support. Shouldn't we try to protect them, too? I commented to this effect on the original article, then realized that I should just write the code myself as proof of concept.

Brian Dillard came up with his own version of a spoiler blockerwhich, through a little progressive enhancement, accommodates for situations where JS is not enabled (eg: a RSS reader). His code consists of two parts; the jQuery code which hides the spoiler and binds the click event to a fade effect and the HTML which is progressive enhanced.

PLAIN TEXT
JAVASCRIPT:
  2. $(document).ready(function() {
  4. $ (".spoiler")
  5. //hide the spoiler
  6. . children("span.hidden").hide()
  7. //hide the whitespace inside it
  8. . children("br").hide()
  9. //step back up a level
  10. . end()
  11. //find the sibling
  12. . prev("span.message")
  13. //add the click handler to show the spoiler
  14. . click(function() {
  15. //use a callback So FX execute non-simultaneously;
  16. $ (this).fadeOut(600, function() {
  17. $ (this).next().fadeIn(600);
  18. })
  19. })
  20. ;
  22. });
PLAIN TEXT
HTML:
  2. <p class="spoiler">
  3. In the movie "Citizen Kane," Charles Foster Kane's last
  4. word, "Rosebud," turns out to be ...
  5. <span class="message">
  6. ( <a href="#answer">Click here if you'd like to be spoiled.</a>)
  7. </span>
  8. <span class="hidden">
  9. <br/ ><br/ ><br/ ><br/ ><br/ ><br/ ><br/ >
  10. <br/ ><br/ ><br/ ><br/ ><br/ ><br/ ><br/ >
  11. <br/ ><br/ ><br/ ><br/ ><br/ ><br/ ><br/ >
  12. <br/ ><br/ ><br/ ><br/ ><br/ ><br/ ><br/ >
  13. <br/ ><br/ ><br/ ><br/ ><br/ ><br/ ><br/ >
  14. <br/ ><br/ ><br/ ><br/ ><br/ ><br/ ><br/ >
  15. <br/ ><br/ ><br/ ><br/ ><br/ ><br/ ><br/ >
  16. <br/ ><br/ ><br/ ><br/ ><br/ ><br/ ><br/ >
  17. <br/ ><br/ ><br/ ><br/ ><br/ ><br/ ><br/ >
  18. <br/ ><br/ ><br/ ><br/ ><br/ ><br/ ><br/ >
  19. <br/ ><br/ ><br/ ><br/ ><br/ ><br/ ><br/ >
  20. <br/ ><br/ ><br/ ><br/ ><br/ ><br/ ><br/ >
  21. <br/ ><br/ ><br/ ><br/ ><br/ ><br/ ><br/ >
  22. <br/ ><br/ ><br/ ><br/ ><br/ ><br/ ><br/ >
  23. <br/ ><br/ ><br/ ><br/ ><br/ ><br/ ><br/ >
  24. <br/ ><br/ ><br/ ><br/ ><br/ ><br/ ><br/ >
  25. <a name="answer"></a>a sled.
  26. </span>
  27. </p>

You can see the demo here. You'll need to turn off JavaScript in order to see it.

This is one way of managing the user experience in user-agents without JavaScript support but I'm sure that the Ajaxian crowd has developed other ways of tackling this same problem. We'd like to hear about it so comment away.

JSJaC

JSJaC is a jabber/XMPP client library written in JavaScript to ease implementation of web based jabber/XMPP clients. For communication with a jabber server it needs to support either HTTP Pollingor XMPP Over BOSH(formerly known as HTTP Binding). JSJaC has an object oriented design which should be quite easy to use. Communication is done by using the XML HTTP Request objectalso refered to as AJAX technology. Your browser must support this.

moo.rd

moo.rdis a super lightweightjavascript (object oriented) library based on the MooTools framework.
It is designed to give many useful and powerful functionalities to the developers, like a lot of effects, customizable standards, utility native functions, table management, virtual boxesand many more.
In addiction moo.rd is modular, flexible, and completely compatiblewith all MooTools plug-in.

Django template

Django’s template language is designed to strike a balance between power and ease. It’s designed to feel comfortable to those used to working with HTML. If you have any exposure to other text-based template languages, such as Smartyor CheetahTemplate, you should feel right at home with Django’s templates.

GWT(Google Web Toolkit)

Google Web Toolkit (GWT) is an open source Java software development framework that makes writing AJAX applications like Google Mapsand Gmaileasy for developers who don't speak browser quirks as a second language. Writing dynamic web applications today is a tedious and error-prone process; you spend 90% of your time working around subtle incompatibilities between web browsers and platforms, and JavaScript's lack of modularity makes sharing, testing, and reusing AJAX components difficult and fragile.

GWT lets you avoid many of these headaches while offering your users the same dynamic, standards-compliant experience. You write your front end in the Javaprogramming language, and the GWT compiler converts your Java classes to browser-compliant JavaScript and HTML.