Author: buildbot
Date: Wed Feb 20 15:29:33 2019
New Revision: 1040659
Log:
Staging update by buildbot for mina
Added:
websites/staging/mina/trunk/content/staticresources/images/mina/incoming-connections.png
(with props)
Modified:
websites/staging/mina/trunk/content/ (props changed)
websites/staging/mina/trunk/content/ftpserver-project/building.html
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
websites/staging/mina/trunk/content/mina-project/userguide/ch9-codec-filter/ch9-codec-filter.html
websites/staging/mina/trunk/content/sshd-project/download_2.1.0.html
Propchange: websites/staging/mina/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Feb 20 15:29:33 2019
@@ -1 +1 @@
-1853950
+1853966
Modified: websites/staging/mina/trunk/content/ftpserver-project/building.html
==============================================================================
--- websites/staging/mina/trunk/content/ftpserver-project/building.html
(original)
+++ websites/staging/mina/trunk/content/ftpserver-project/building.html Wed Feb
20 15:29:33 2019
@@ -133,7 +133,7 @@ h2:hover > .headerlink, h3:hover > .head
}
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
<h1 id="building">Building<a class="headerlink" href="#building"
title="Permanent link">¶</a></h1>
-<p>You need <a href="http://svnbook.red-bean.com/";>Subversion</a> to <a
href="http://apache.org/dev/version-control.html";>check out the source code</a>
from <a href="getting_sources.html">our source code repository</a>, and <a
href="http://maven.apache.org/download.html";>Maven 2</a> to build the source
code. Currently, Maven 2.0.5 or 2.0.7 or newer is required for the build.</p>
+<p>You need <a href="http://svnbook.red-bean.com/";>Subversion</a> to <a
href="http://apache.org/dev/version-control.html";>check out the source code</a>
from <a href="getting_source.html">our source code repository</a>, and <a
href="http://maven.apache.org/download.html";>Maven 2</a> to build the source
code. Currently, Maven 2.0.5 or 2.0.7 or newer is required for the build.</p>
<p>The following example shows how to build the trunk.</p>
<div class="codehilite"><pre>$ <span class="n">svn</span> <span
class="n">co</span> <span class="n">http</span><span class="p">:</span><span
class="o">//</span><span class="n">svn</span><span class="p">.</span><span
class="n">apache</span><span class="p">.</span><span class="n">org</span><span
class="o">/</span><span class="n">repos</span><span class="o">/</span><span
class="n">asf</span><span class="o">/</span><span class="n">mina</span><span
class="o">/</span><span class="n">ftpserver</span><span class="o">/</span><span
class="n">trunk</span><span class="o">/</span> <span class="n">ftpserver</span>
$ <span class="n">cd</span> <span class="n">ftpserver</span>
Modified:
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
==============================================================================
---
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
(original)
+++
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
Wed Feb 20 15:29:33 2019
@@ -274,7 +274,7 @@ Be aware that if the remote peer is not
</ul>
<p>plus other configuration, depending on the transport type used (see Chapter
6 - Transports).</p>
<p>All those configuration parameters are stored into the
<em>IoSessionConfig</em> object, which can be get from the session using the
<em>session.getConfig()</em> method.</p>
-<p>For further informations about the session configuration, see <a
href="ch4-session/ch4.1-session-configuration.html">Chapter 4.1 - Session
Configuration</a></p>
+<p>For further informations about the session configuration, see <a
href="ch4.1-session-configuration.html">Chapter 4.1 - Session
Configuration</a></p>
<h2 id="managing-user-defined-attributes">Managing user-defined attributes<a
class="headerlink" href="#managing-user-defined-attributes" title="Permanent
link">¶</a></h2>
<p>It might be necessary to store some data which may be used later. This is
done using the dedicated data structure associated which each session. This is
a key-value association, which can store any type of data the developer might
want to keep remanent along the session's life.</p>
<p>For instance, if you want to track the number of request a user has sent
since the session has been created, it's easy to store it into this map: just
create a key that will be associated with this value.</p>
@@ -347,7 +347,7 @@ Be aware that if the remote peer is not
<li>throughput</li>
</ul>
<p>and many other useful informations.</p>
-<p>For further informations about the session statistics, see <a
href="ch4-session/ch4.2-session-statistics.html">Chapter 4.2 - Session
Statistics</a></p>
+<p>For further informations about the session statistics, see <a
href="ch4.2-session-statistics.html">Chapter 4.2 - Session Statistics</a></p>
<h2 id="handler">Handler<a class="headerlink" href="#handler" title="Permanent
link">¶</a></h2>
<p>Last, not least, a session is attached to a Handler, in charge of
dispatching the messages to your application. This handler will also send back
response by using the session, simply by calling the write() method :</p>
<div class="codehilite"><pre><span class="o">...</span>
Modified:
websites/staging/mina/trunk/content/mina-project/userguide/ch9-codec-filter/ch9-codec-filter.html
==============================================================================
---
websites/staging/mina/trunk/content/mina-project/userguide/ch9-codec-filter/ch9-codec-filter.html
(original)
+++
websites/staging/mina/trunk/content/mina-project/userguide/ch9-codec-filter/ch9-codec-filter.html
Wed Feb 20 15:29:33 2019
@@ -452,7 +452,7 @@ In this case the message has a fixed siz
<li>MINA ensures that there will never be more than one thread simultaneously
executing the decode() function for the same IoSession, but it does not
guarantee that it will always be the same thread. Suppose the first piece of
data is handled by thread-1 who decides it cannot yet decode, when the next
piece of data arrives, it could be handled by another thread. To avoid
visibility problems, you must properly synchronize access to this decoder state
(IoSession attributes are stored in a ConcurrentHashMap, so they are
automatically visible to other threads).</li>
<li>a discussion on the mailing list has lead to this conclusion: choosing
between storing state in the IoSession or in the Decoder instance itself is
more a matter of taste. To ensure that no two threads will run the decode
method for the same IoSession, MINA needs to do some form of synchronization
=> this synchronization will also ensure you can't have the visibility
problem described above.
(Thanks to Adam Fisk for pointing this out)
-see <a
href="http://www.nabble.com/Tutorial-on-ProtocolCodecFilter,-state-and-threads-t3965413.html";>http://www.nabble.com/Tutorial-on-ProtocolCodecFilter,-state-and-threads-t3965413.html</a></li>
+see <a
href="https://www.mail-archive.com/dev@mina.apache.org/msg03038.html";>https://www.mail-archive.com/dev@mina.apache.org/msg03038.html</a></li>
</ul>
</li>
<li>IoBuffer.prefixedDataAvailable() is very convenient when your protocol
uses a length-prefix; it supports a prefix of 1, 2 or 4 bytes.</li>
Modified: websites/staging/mina/trunk/content/sshd-project/download_2.1.0.html
==============================================================================
--- websites/staging/mina/trunk/content/sshd-project/download_2.1.0.html
(original)
+++ websites/staging/mina/trunk/content/sshd-project/download_2.1.0.html Wed
Feb 20 15:29:33 2019
@@ -145,10 +145,6 @@ h2:hover > .headerlink, h3:hover > .head
<li><a
href="https://www.apache.org/dyn/closer.lua/mina/sshd/2.1.0/apache-sshd-2.1.0.zip";>Apache
Mina SSHD 2.1.0 Binary (.zip)</a> <a
href="https://archive.apache.org/dist/mina/sshd/2.1.0/apache-sshd-2.1.0.zip.asc";>PGP</a>
<a
href="https://archive.apache.org/dist/mina/sshd/2.1.0/apache-sshd-2.1.0.zip.sha1";>SHA</a></li>
</ul>
</li>
-<li>Individual jars:<ul>
-<li><a
href="https://www.apache.org/dyn/closer.lua/mina/sshd/2.1.0/sshd-core-2.1.0.jar";>Apache
Mina SSHD Core 2.1.0 (.jar)</a> <a
href="https://archive.apache.org/dist/mina/sshd/2.1.0/sshd-core-2.1.0.jar.asc";>PGP</a>
<a
href="https://archive.apache.org/dist/mina/sshd/2.1.0/sshd-core-2.1.0.jar.sha1";>SHA</a></li>
-</ul>
-</li>
</ul>
<h1 id="release-notes">Release Notes<a class="headerlink"
href="#release-notes" title="Permanent link">¶</a></h1>
<p>A few backward incompatible changes have been made since the previous
release, thus the version has been named 2.1 accordingly, in order to emphasize
this fact. The major issues addressed in this release are:</p>
Added:
websites/staging/mina/trunk/content/staticresources/images/mina/incoming-connections.png
==============================================================================
Binary file - no diff available.
Propchange:
websites/staging/mina/trunk/content/staticresources/images/mina/incoming-connections.png
------------------------------------------------------------------------------
svn:mime-type = image/png
