<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Overview</title><link>https://sourceforge.net/p/multiprocessing/wiki/Overview/</link><description>Recent changes to Overview</description><atom:link href="https://sourceforge.net/p/multiprocessing/wiki/Overview/feed" rel="self"/><language>en</language><lastBuildDate>Thu, 24 Oct 2024 18:12:33 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/multiprocessing/wiki/Overview/feed" rel="self" type="application/rss+xml"/><item><title>Overview modified by ENGITEX</title><link>https://sourceforge.net/p/multiprocessing/wiki/Overview/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v27
+++ v28
@@ -30,6 +30,6 @@
 See also:
 [Concepts]
 [System requirements]
-[API reference]
+[Remote code loading]
 [Examples of use cases]
 [Node admin panel]
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ENGITEX</dc:creator><pubDate>Thu, 24 Oct 2024 18:12:33 -0000</pubDate><guid>https://sourceforge.netd99a55f81e297fa3bf1127118bbc6cce509523cf</guid></item><item><title>Overview modified by ENGITEX</title><link>https://sourceforge.net/p/multiprocessing/wiki/Overview/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v26
+++ v27
@@ -4,9 +4,9 @@

 Similar options are available in C++ as discussed here [Parallel computing in C++ vs. Java by ENGITEX](https://www.linkedin.com/pulse/parallel-computing-c-vs-java-engitex-zfz1e/?trackingId=E8lu6xoNrirvWi8BWu6L%2Fw%3D%3D)

-None of these assume a distributed system by default. This is the primary goal of JMP package.
-Unlike older tools, JMP also allows setting affinity for new processes explicitly instead of relying on the OS.
-Another perk made available with Java RMI is **remote (dynamic) code loading** which offers a new look on client-server software design. 
+▪ None of these assume a distributed system by default. This is the primary goal of JMP package.
+▪ Unlike older tools, JMP also allows setting affinity for new processes explicitly instead of relying on the OS.
+▪ Another perk made available with Java RMI is **remote (dynamic) code loading** which offers a new look on client-server software design. 

 ### JMP overview

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ENGITEX</dc:creator><pubDate>Thu, 24 Oct 2024 17:57:50 -0000</pubDate><guid>https://sourceforge.netb623b23ccee8544f2da115924d2511c32afab415</guid></item><item><title>Overview modified by ENGITEX</title><link>https://sourceforge.net/p/multiprocessing/wiki/Overview/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v25
+++ v26
@@ -14,7 +14,7 @@

 JMP relies on [RMI](https://docs.oracle.com/javase/tutorial/rmi/index.html) for inter-process communication both on local and remote machines and uses modern Windows PowerShell for communications with the OS.

-In addition to **running a separate process asynchronously**, Java Multiprocessing naturally incorporates **a cluster management and load balancing tool**. The tool takes care of load balancing between several CPUs, both on local and remote machines. A desktop running JMP server (i.e. JMP ***node*** class) might have its "slave" nodes for load distribution.
+In addition to **running a separate process asynchronously**, Java Multiprocessing naturally incorporates **a cluster management and load balancing tool**. The tool takes care of load balancing between several CPUs, both on local and remote machines. A desktop running JMP server (a.k.a. JMP ***node*** ) might have its "slave" nodes for load distribution.

 Java Multiprocessing scheme gives a general idea how JMP works - cluster management classes and methods rely on multiprocessing methods:
 ![UML](https://i.ibb.co/MNd7kgP/UML-small.png)
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ENGITEX</dc:creator><pubDate>Thu, 24 Oct 2024 17:50:46 -0000</pubDate><guid>https://sourceforge.net692ebbf6644603c3c27f50e89bcd00919986db9d</guid></item><item><title>Overview modified by ENGITEX</title><link>https://sourceforge.net/p/multiprocessing/wiki/Overview/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v24
+++ v25
@@ -32,3 +32,4 @@
 [System requirements]
 [API reference]
 [Examples of use cases]
+[Node admin panel]
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ENGITEX</dc:creator><pubDate>Thu, 24 Oct 2024 17:47:15 -0000</pubDate><guid>https://sourceforge.net36836374966b96a23f1fbf522030b767683d38b0</guid></item><item><title>Overview modified by ENGITEX</title><link>https://sourceforge.net/p/multiprocessing/wiki/Overview/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v23
+++ v24
@@ -5,6 +5,7 @@
 Similar options are available in C++ as discussed here [Parallel computing in C++ vs. Java by ENGITEX](https://www.linkedin.com/pulse/parallel-computing-c-vs-java-engitex-zfz1e/?trackingId=E8lu6xoNrirvWi8BWu6L%2Fw%3D%3D)

 None of these assume a distributed system by default. This is the primary goal of JMP package.
+Unlike older tools, JMP also allows setting affinity for new processes explicitly instead of relying on the OS.
 Another perk made available with Java RMI is **remote (dynamic) code loading** which offers a new look on client-server software design. 

 ### JMP overview
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ENGITEX</dc:creator><pubDate>Thu, 24 Oct 2024 16:02:48 -0000</pubDate><guid>https://sourceforge.neta92bb9f769a24a3eea3e559f3c40f0a893b3c3c6</guid></item><item><title>Overview modified by ENGITEX</title><link>https://sourceforge.net/p/multiprocessing/wiki/Overview/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v22
+++ v23
@@ -5,7 +5,7 @@
 Similar options are available in C++ as discussed here [Parallel computing in C++ vs. Java by ENGITEX](https://www.linkedin.com/pulse/parallel-computing-c-vs-java-engitex-zfz1e/?trackingId=E8lu6xoNrirvWi8BWu6L%2Fw%3D%3D)

 None of these assume a distributed system by default. This is the primary goal of JMP package.
-Another perk made available with Java RMI is remote (dynamic) code loading which offers a new look on client-server software design. 
+Another perk made available with Java RMI is **remote (dynamic) code loading** which offers a new look on client-server software design. 

 ### JMP overview

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ENGITEX</dc:creator><pubDate>Thu, 24 Oct 2024 15:37:36 -0000</pubDate><guid>https://sourceforge.netda0a03438a457abb92eddd7be66dbf487dd08fbf</guid></item><item><title>Overview modified by ENGITEX</title><link>https://sourceforge.net/p/multiprocessing/wiki/Overview/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v21
+++ v22
@@ -9,7 +9,7 @@

 ### JMP overview

-Java MultiProcessing is a library with API that resembles [Java Multithreading](https://docs.oracle.com/javase/tutorial/essential/concurrency/runthread.html) which is an essential built-in Java feature. The library's core component allows running a piece of Java code (further referenced as ***task***) on a separate process.
+Java MultiProcessing is a library with API that resembles [Java Multithreading](https://docs.oracle.com/javase/tutorial/essential/concurrency/runthread.html) which is an essential built-in Java feature. The library's core component allows running a piece of Java code (further referenced as ***task***) asynchronously on a separate process.

 JMP relies on [RMI](https://docs.oracle.com/javase/tutorial/rmi/index.html) for inter-process communication both on local and remote machines and uses modern Windows PowerShell for communications with the OS.

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ENGITEX</dc:creator><pubDate>Thu, 24 Oct 2024 15:35:51 -0000</pubDate><guid>https://sourceforge.net723944600316eaba74304d3bb1e8aa2f16c922ef</guid></item><item><title>Overview modified by ENGITEX</title><link>https://sourceforge.net/p/multiprocessing/wiki/Overview/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v20
+++ v21
@@ -2,7 +2,7 @@

 With a rapid development of multicore PCs, high-performance computing clusters and with client-server architecture becoming omnipresent, the standard hardware-agnostic approach to load distribution on a local machine provided in Java might not be suitable for the tasks.

-Similar options are available in C++ as discussed here [Parallel computing in Java vs. C++ by ENGITEX](https://www.linkedin.com/pulse/parallel-computing-c-vs-java-engitex-zfz1e/?trackingId=E8lu6xoNrirvWi8BWu6L%2Fw%3D%3D)
+Similar options are available in C++ as discussed here [Parallel computing in C++ vs. Java by ENGITEX](https://www.linkedin.com/pulse/parallel-computing-c-vs-java-engitex-zfz1e/?trackingId=E8lu6xoNrirvWi8BWu6L%2Fw%3D%3D)

 None of these assume a distributed system by default. This is the primary goal of JMP package.
 Another perk made available with Java RMI is remote (dynamic) code loading which offers a new look on client-server software design. 
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ENGITEX</dc:creator><pubDate>Thu, 24 Oct 2024 15:34:05 -0000</pubDate><guid>https://sourceforge.net99a219de25b3455fe916cd1cac952413f3b44a02</guid></item><item><title>Overview modified by ENGITEX</title><link>https://sourceforge.net/p/multiprocessing/wiki/Overview/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v19
+++ v20
@@ -2,18 +2,18 @@

 With a rapid development of multicore PCs, high-performance computing clusters and with client-server architecture becoming omnipresent, the standard hardware-agnostic approach to load distribution on a local machine provided in Java might not be suitable for the tasks.

-Similar options are available in C++ as discussed here https://www.linkedin.com/pulse/parallel-computing-c-vs-java-engitex-zfz1e/?trackingId=E8lu6xoNrirvWi8BWu6L%2Fw%3D%3D
+Similar options are available in C++ as discussed here [Parallel computing in Java vs. C++ by ENGITEX](https://www.linkedin.com/pulse/parallel-computing-c-vs-java-engitex-zfz1e/?trackingId=E8lu6xoNrirvWi8BWu6L%2Fw%3D%3D)

 None of these assume a distributed system by default. This is the primary goal of JMP package.
 Another perk made available with Java RMI is remote (dynamic) code loading which offers a new look on client-server software design. 

 ### JMP overview

-Java Multiprocessing is a library with API that resembles [Java Multithreading](https://docs.oracle.com/javase/tutorial/essential/concurrency/runthread.html) which is an essential built-in Java feature. The library allows easily running a piece of code on a separate process.
+Java MultiProcessing is a library with API that resembles [Java Multithreading](https://docs.oracle.com/javase/tutorial/essential/concurrency/runthread.html) which is an essential built-in Java feature. The library's core component allows running a piece of Java code (further referenced as ***task***) on a separate process.

-Java Multiprocessing relies on [RMI](https://docs.oracle.com/javase/tutorial/rmi/index.html) for inter-process communication and uses modern Windows PowerShell for communications with the OS.
+JMP relies on [RMI](https://docs.oracle.com/javase/tutorial/rmi/index.html) for inter-process communication both on local and remote machines and uses modern Windows PowerShell for communications with the OS.

-In addition to **running a separate process asynchronously**, Java Multiprocessing naturally incorporates **a cluster management and load balancing tool**. The tool takes care of load balancing between several CPUs, both on local and remote machines. A desktop running JMP server (i.e. JMP node class) might have its "slave" nodes for load distribution.
+In addition to **running a separate process asynchronously**, Java Multiprocessing naturally incorporates **a cluster management and load balancing tool**. The tool takes care of load balancing between several CPUs, both on local and remote machines. A desktop running JMP server (i.e. JMP ***node*** class) might have its "slave" nodes for load distribution.

 Java Multiprocessing scheme gives a general idea how JMP works - cluster management classes and methods rely on multiprocessing methods:
 ![UML](https://i.ibb.co/MNd7kgP/UML-small.png)
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ENGITEX</dc:creator><pubDate>Thu, 24 Oct 2024 15:33:40 -0000</pubDate><guid>https://sourceforge.net741aa08307b5294d16ba94530618db3cede7594c</guid></item><item><title>Overview modified by ENGITEX</title><link>https://sourceforge.net/p/multiprocessing/wiki/Overview/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v18
+++ v19
@@ -2,7 +2,7 @@

 With a rapid development of multicore PCs, high-performance computing clusters and with client-server architecture becoming omnipresent, the standard hardware-agnostic approach to load distribution on a local machine provided in Java might not be suitable for the tasks.

-Similar options are available with C++ as discussed here https://www.linkedin.com/pulse/parallel-computing-c-vs-java-engitex-zfz1e/?trackingId=E8lu6xoNrirvWi8BWu6L%2Fw%3D%3D
+Similar options are available in C++ as discussed here https://www.linkedin.com/pulse/parallel-computing-c-vs-java-engitex-zfz1e/?trackingId=E8lu6xoNrirvWi8BWu6L%2Fw%3D%3D

 None of these assume a distributed system by default. This is the primary goal of JMP package.
 Another perk made available with Java RMI is remote (dynamic) code loading which offers a new look on client-server software design. 
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ENGITEX</dc:creator><pubDate>Thu, 24 Oct 2024 15:28:14 -0000</pubDate><guid>https://sourceforge.net3f15e773da100095e8a0873b7a0fc5671c33becd</guid></item></channel></rss>