Until now, we’ve always had concurrent program working in one virtual machines, but JR provides ways to declare several virtual machines on several different physical machines. A JR Virtual Machine contains a Java Virtual Machine and a layer for the JR language. Once you created some virtual machines, you can specify where an object will be created with a variant of the new operator. …

In this post, we’ll see a new feature of JR : the rendezvous.
Like asynchronous message passing, this synchronization method involves two processes : a caller and a receiver. But this time, the invocation is synchronous, the caller delays until the operation completes. The rendezvous does not create a new thread to the receiver. The receiver must invoke an input statement (the implementation of rendezvous) …

We’ve now covered the basic synchronization systems (semaphore, monitors) and we know how to declare operations and capabilities . It’s time to go to an other form of synchronization : Message Passing. In this post, we’ll focus in Asynchronous Message Passing, we’ll cover later, the synchronous message passing system with RendezVous.
When we use message passing, the threads doesn’t share datas anymore, they share channels. …

Like I promised, I will restart to write articles now that the evaluation period is over.
After seeing how to develop using the JR programming language, we’ll see now how to use monitors in JR.
Monitors provide a higher-level abstraction than semaphores and produce a better code with several advantages :

All the synchronization code is centralized in one location and the users of this code …