<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Frameworks</title><link>https://sourceforge.net/p/molstream/wiki/Frameworks/</link><description>Recent changes to Frameworks</description><atom:link href="https://sourceforge.net/p/molstream/wiki/Frameworks/feed" rel="self"/><language>en</language><lastBuildDate>Tue, 01 Jul 2014 09:59:48 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/molstream/wiki/Frameworks/feed" rel="self" type="application/rss+xml"/><item><title>Frameworks modified by Alex Libov</title><link>https://sourceforge.net/p/molstream/wiki/Frameworks/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v1
+++ v2
@@ -23,7 +23,7 @@
 
 ~~~~~~

-When the role is "server", the node acts as a source - it generates stream chunks and expects messages from the specified port.
+When the role is "server", the node acts as a source - it generates stream chunks and expects messages in the specified port.

 ~~~~~~
 
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex Libov</dc:creator><pubDate>Tue, 01 Jul 2014 09:59:48 -0000</pubDate><guid>https://sourceforge.net245d81eeaf5ecdec1639e721bcb3dd5d51612b78</guid></item><item><title>Frameworks modified by Alex Libov</title><link>https://sourceforge.net/p/molstream/wiki/Frameworks/</link><description>&lt;div class="markdown_content"&gt;&lt;h2 id="frameworks"&gt;Frameworks&lt;/h2&gt;
&lt;p&gt;The Framework element sets the network framework to be used by the system. &lt;br /&gt;
MOLStream currently supports the following frameworks:&lt;/p&gt;
&lt;h6 id="peersim"&gt;Peersim&lt;/h6&gt;
&lt;p&gt;This framework runs on a single machine, and simulates the P2P network using the Peersim P2P simulator.&lt;br /&gt;
The runs are fully reproducible and should be identical if run using the same seed.&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="n"&gt;framework&lt;/span&gt; &lt;span class="n"&gt;value&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;&amp;quot;PeerSimFramework&amp;quot;&lt;/span&gt; &lt;span class="n"&gt;dropRate&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;&amp;quot;0.0&amp;quot;&lt;/span&gt; &lt;span class="n"&gt;minDelay&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;&amp;quot;200&amp;quot;&lt;/span&gt; &lt;span class="n"&gt;maxDelay&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;&amp;quot;400&amp;quot;&lt;/span&gt; &lt;span class="o"&gt;/&amp;gt;&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;p&gt;PeerSimFramework element receives three arguments: the dropRate of messages (from 0.0 to 1.0)&lt;br /&gt;
and a minimal and maximal delay of messages (in milliseconds). The delay of messages is distributed uniformly between minDelay and maxDelay. Each message is being sent with a new random delay, however, FIFO order is preserved.&lt;/p&gt;
&lt;h6 id="network"&gt;Network&lt;/h6&gt;
&lt;p&gt;The network framework sends UDP messages. Each invocation of MOLStream generates all clients on a single machine. MOLStream has to be invoked on every machine with matching xml configuration files.&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="n"&gt;framework&lt;/span&gt; &lt;span class="n"&gt;value&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;&amp;quot;NetworkFramework&amp;quot;&lt;/span&gt; &lt;span class="n"&gt;role&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;&amp;quot;server&amp;quot;&lt;/span&gt; &lt;span class="n"&gt;port&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;&amp;quot;8000&amp;quot;&lt;/span&gt; &lt;span class="o"&gt;/&amp;gt;&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;p&gt;When the role is "server", the node acts as a source - it generates stream chunks and expects messages from the specified port.&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span class="nt"&gt;&amp;lt;framework&lt;/span&gt; &lt;span class="na"&gt;value=&lt;/span&gt;&lt;span class="s"&gt;&amp;quot;NetworkFramework&amp;quot;&lt;/span&gt; &lt;span class="na"&gt;role=&lt;/span&gt;&lt;span class="s"&gt;&amp;quot;client&amp;quot;&lt;/span&gt; &lt;span class="na"&gt;port=&lt;/span&gt;&lt;span class="s"&gt;&amp;quot;8001&amp;quot;&lt;/span&gt; &lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;address&lt;/span&gt; &lt;span class="na"&gt;port=&lt;/span&gt;&lt;span class="s"&gt;&amp;quot;8000&amp;quot;&lt;/span&gt; &lt;span class="na"&gt;hostname=&lt;/span&gt;&lt;span class="s"&gt;&amp;quot;serverHostName&amp;quot;&lt;/span&gt; &lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/framework&amp;gt;&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;p&gt;When the role is "client", the node acts as a user. the port specified in the framework element is the port used for sending and receiving UDP messages. The address element specifies the hostname and port of the source node and should match the hostname and port of the node in which MOLStream was invoked with the role "server".&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex Libov</dc:creator><pubDate>Tue, 01 Jul 2014 09:58:58 -0000</pubDate><guid>https://sourceforge.neta91486079f5efe7b236a5d97479600726a5ef08d</guid></item></channel></rss>