You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mina.apache.org by bu...@apache.org on 2015/11/10 09:41:56 UTC
svn commit: r971954 [4/9] - in /websites/staging/mina/trunk/content: ./
asyncweb-project/ ftpserver-project/ mina-project/ mina-project/userguide/
mina-project/userguide/ch1-getting-started/
mina-project/userguide/ch10-executor-filter/ mina-project/use...
Modified: websites/staging/mina/trunk/content/ftpserver-project/running_ftpserver_standalone.html
==============================================================================
--- websites/staging/mina/trunk/content/ftpserver-project/running_ftpserver_standalone.html (original)
+++ websites/staging/mina/trunk/content/ftpserver-project/running_ftpserver_standalone.html Tue Nov 10 08:41:53 2015
@@ -72,7 +72,18 @@
- <div id="navigation">
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<div id="navigation">
<h5>Overview</h5>
<ul>
<li><a href="./../ftpserver-project/index.html">Home</a> </li>
@@ -110,9 +121,20 @@
<div id="rightColumn">
-<h1 id="running-ftpserver-stand-alone-in-5-minutes">Running FtpServer stand-alone in 5 minutes</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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="running-ftpserver-stand-alone-in-5-minutes">Running FtpServer stand-alone in 5 minutes<a class="headerlink" href="#running-ftpserver-stand-alone-in-5-minutes" title="Permanent link">¶</a></h1>
<p>To get FtpServer up and running in stand-alone mode, you need to have a full distribution. Check out to build the source code and make sure you include the build for the distribution module</p>
-<h2 id="installing">Installing</h2>
+<h2 id="installing">Installing<a class="headerlink" href="#installing" title="Permanent link">¶</a></h2>
<p>Now you should have a ZIP or TARed file with the entire distribution. Let's go.</p>
<p>First of all, unpack it. If you're on Linux/Unix, you can use:</p>
<div class="codehilite"><pre><span class="n">tar</span> <span class="o">-</span><span class="n">xzvf</span> <span class="n">ftpserver</span><span class="o">-</span>1<span class="p">.</span>0<span class="p">.</span>0<span class="p">.</span><span class="n">tar</span><span class="p">.</span><span class="n">gz</span>
@@ -120,7 +142,7 @@
<p>On Windows and Linux/Unix, you can use any ZIP tool, like <a href="http://www.7-zip.org/">7-zip</a> or <a href="http://fileroller.sourceforge.net/">Gnome File Roller</a> to unzip the file at a location of your liking.</p>
-<h2 id="running-a-basic-server">Running a basic server</h2>
+<h2 id="running-a-basic-server">Running a basic server<a class="headerlink" href="#running-a-basic-server" title="Permanent link">¶</a></h2>
<p>Now, open a shell/command prompt where you unpacked the files. On Linux/Unix, run:</p>
<div class="codehilite"><pre><span class="n">bin</span><span class="o">/</span><span class="n">ftpd</span><span class="p">.</span><span class="n">sh</span>
</pre></div>
@@ -133,7 +155,7 @@
<p>FtpServer should now start as expected and you should be able to use a FTP client to access the server at localhost on port 21. The default .</p>
<p>Note that on Linux this command will require root privileges as it tried to listen on port 21, something only root can do. If you're not root, you will get an exception saying "java.net.SocketException: Permission denied". Let's have a look at how to solve this without running as root.</p>
-<h2 id="configuring">Configuring</h2>
+<h2 id="configuring">Configuring<a class="headerlink" href="#configuring" title="Permanent link">¶</a></h2>
<p>In the res/conf directory in the unpackaged directory you will find some example configuration files. For this tutorial, we will use the ftpd-typical.xml configuration file. It will set the listener port to 2121, thus fixing the issue with not being able to run the server as non-root on Linux. It will also use a provided user database, allowing logging in as admin (password admin) or anonymous. To run, on Linux/Unix:</p>
<div class="codehilite"><pre><span class="n">bin</span><span class="o">/</span><span class="n">ftpd</span><span class="p">.</span><span class="n">sh</span> <span class="n">res</span><span class="o">/</span><span class="n">conf</span><span class="o">/</span><span class="n">ftpd</span><span class="o">-</span><span class="n">typical</span><span class="p">.</span><span class="n">xml</span>
</pre></div>
Modified: websites/staging/mina/trunk/content/ftpserver-project/testimonials.html
==============================================================================
--- websites/staging/mina/trunk/content/ftpserver-project/testimonials.html (original)
+++ websites/staging/mina/trunk/content/ftpserver-project/testimonials.html Tue Nov 10 08:41:53 2015
@@ -72,7 +72,18 @@
- <div id="navigation">
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<div id="navigation">
<h5>Overview</h5>
<ul>
<li><a href="./../ftpserver-project/index.html">Home</a> </li>
@@ -110,7 +121,18 @@
<div id="rightColumn">
-<h1 id="testimonials">Testimonials</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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="testimonials">Testimonials<a class="headerlink" href="#testimonials" title="Permanent link">¶</a></h1>
<p><strong>Daniel Frank</strong> says:</p>
<blockquote>
<p>Apache FtpServer has proven to be a stable and reliable platform for our
Modified: websites/staging/mina/trunk/content/index.html
==============================================================================
--- websites/staging/mina/trunk/content/index.html (original)
+++ websites/staging/mina/trunk/content/index.html Tue Nov 10 08:41:53 2015
@@ -82,7 +82,7 @@
<ul>
<li><a href="./downloads-mina.html">Mina 2.0.9</a></li>
<li><a href="./downloads-ftpserver.html">FtpServer 1.0.6</a></li>
- <li><a href="./downloads-sshd.html">SSHD 0.14.0</a></li>
+ <li><a href="./downloads-sshd.html">SSHD 1.0.0</a></li>
<li><a href="./downloads-vysper.html">Vysper 0.7</a></li>
</ul>
<h5>Projects</h5>
@@ -119,6 +119,17 @@
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
<p>Apache MINA is a network application framework which helps users develop high performance and high scalability network applications easily. It provides an abstract event-driven asynchronous API over various transports such as TCP/IP and UDP/IP via Java NIO.</p>
<p>Apache MINA is often called:</p>
<ul>
Modified: websites/staging/mina/trunk/content/mailing-lists.html
==============================================================================
--- websites/staging/mina/trunk/content/mailing-lists.html (original)
+++ websites/staging/mina/trunk/content/mailing-lists.html Tue Nov 10 08:41:53 2015
@@ -82,7 +82,7 @@
<ul>
<li><a href="./downloads-mina.html">Mina 2.0.9</a></li>
<li><a href="./downloads-ftpserver.html">FtpServer 1.0.6</a></li>
- <li><a href="./downloads-sshd.html">SSHD 0.14.0</a></li>
+ <li><a href="./downloads-sshd.html">SSHD 1.0.0</a></li>
<li><a href="./downloads-vysper.html">Vysper 0.7</a></li>
</ul>
<h5>Projects</h5>
@@ -119,6 +119,17 @@
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
<p>The Apache MINA team interacts with MINA developers and users via <a href="http://en.wikipedia.org/wiki/Mailing_list">mailing lists</a>. If you have any questions or something to say to us, please subscribe to our user mailing list and post a message. If you would like to contribute to the development of MINA, please subscribe to the developer mailing list.</p>
<p><strong>Do NOT cross post (ie mail to users and dev). Pick the right list</strong></p>
<p>Take a few minutes to read this page :<a href="http://www.catb.org/~esr/faqs/smart-questions.html">Asking Smart Questions</a></p>
@@ -133,30 +144,30 @@
<li>Don't be afraid to post, even if you think your english suck. Most of us are not english native speakers, anyways ...</li>
</ul>
<p>Thanks for listening !</p>
-<h1 id="users-mailing-list">Users mailing list</h1>
+<h1 id="users-mailing-list">Users mailing list<a class="headerlink" href="#users-mailing-list" title="Permanent link">¶</a></h1>
<p>This list is for any questions related to MINA. It's where you need to post for requesting support, or asking question about API usage.</p>
-<h2 id="subscribing">Subscribing</h2>
+<h2 id="subscribing">Subscribing<a class="headerlink" href="#subscribing" title="Permanent link">¶</a></h2>
<p>Send a message to <a href="mailto:users-subscribe@mina.apache.org">users-subscribe@mina.apache.org</a> with a subject and body containg 'subscribe'. You can actually send an empty or rich text message to unsubscribe, but our spam filter might reject your message. After sending your initial email, you will be sent a confirmation email. Simply reply to the confirmation email and you will be subscribed.</p>
-<h2 id="posting-a-message">Posting a message</h2>
+<h2 id="posting-a-message">Posting a message<a class="headerlink" href="#posting-a-message" title="Permanent link">¶</a></h2>
<p>You can ask any questions or provide feedback by sending an email to <a href="mailto:users@mina.apache.org">users@mina.apache.org</a> after subscribing to the mailing list. Your message can be sent even if you didn't subscribe to the mailing list, but it will take some time for your message to be in our mail box because of the moderation process.</p>
-<h2 id="unsubscribing">Unsubscribing</h2>
+<h2 id="unsubscribing">Unsubscribing<a class="headerlink" href="#unsubscribing" title="Permanent link">¶</a></h2>
<p>Oh, did you lose your interest in MINA? Please let us know what made so if MINA couldn't solve your problem and give it a chance! Sending a message whose subject and body contains 'unsubscribe' to <a href="mailto:users-unsubscribe@mina.apache.org">users-unsubscribe@mina.apache.org</a> in plain text format will unsubscribe you from the mailing list though. You can actually send an empty or rich text message to unsubscribe, but our spam filter might reject your message.</p>
-<h1 id="developers-mailing-list">Developers mailing list</h1>
+<h1 id="developers-mailing-list">Developers mailing list<a class="headerlink" href="#developers-mailing-list" title="Permanent link">¶</a></h1>
<p>This mailing list is used for discussions about the actual development of MINA and sub-projects (Ftpserver, Asyncweb).</p>
-<h2 id="subscribing_1">Subscribing</h2>
+<h2 id="subscribing_1">Subscribing<a class="headerlink" href="#subscribing_1" title="Permanent link">¶</a></h2>
<p>Similar to subscribing to the user mailing list, please send a message whose subject and body contains 'subscribe' to <a href="mailto:dev-subscribe@mina.apache.org">dev-subscribe@mina.apache.org</a> in plain text format. Again, you can actually send an empty or rich text message to subscribe, but our spam filter might reject your message</p>
-<h2 id="posting-a-message_1">Posting a message</h2>
+<h2 id="posting-a-message_1">Posting a message<a class="headerlink" href="#posting-a-message_1" title="Permanent link">¶</a></h2>
<p>You can ask any questions or feedback to <a href="mailto:dev@mina.apache.org">dev@mina.apache.org</a> after subscribing to the mailing list. Your message can be sent even if you didn't subscribe to the mailing list, but it will take for some time for your message to be in our mail box because of moderation process.</p>
<p>Alternatively, you can use the web forum interface.</p>
-<h2 id="unsubscribing-from-the-mailing-list">Unsubscribing from the mailing list</h2>
+<h2 id="unsubscribing-from-the-mailing-list">Unsubscribing from the mailing list<a class="headerlink" href="#unsubscribing-from-the-mailing-list" title="Permanent link">¶</a></h2>
<p>To unsubscribe, send a message whose subject and body contains 'unsubscribe' to <a href="mailto:dev-unsubscribe@mina.apache.org">dev-unsubscribe@mina.apache.org</a> in plain text format will unsubscribe you from the mailing list though. You can actually send an empty or rich text message to unsubscribe, but our spam filter might reject your message</p>
-<h1 id="commits-mailing-list">Commits mailing list</h1>
+<h1 id="commits-mailing-list">Commits mailing list<a class="headerlink" href="#commits-mailing-list" title="Permanent link">¶</a></h1>
<p>This mailing list is tracking all the code modifications realised in MINA subversion repository. It's an useful tool for knowing what is going on MINA development and giving feeback on last modifications using the development mailing list</p>
-<h2 id="subscribing_2">Subscribing</h2>
+<h2 id="subscribing_2">Subscribing<a class="headerlink" href="#subscribing_2" title="Permanent link">¶</a></h2>
<p>Similar to subscribing to the user and developer mailing lists, please send a message whose subject and body contains 'subscribe' to <a href="mailto:commits-subscribe@mina.apache.org">commits-subscribe@mina.apache.org</a> in plain text format. Again, you can actually send an empty or rich text message to subscribe, but our spam filter might reject your message</p>
-<h2 id="unsubscribing-from-the-mailing-list_1">Unsubscribing from the mailing list</h2>
+<h2 id="unsubscribing-from-the-mailing-list_1">Unsubscribing from the mailing list<a class="headerlink" href="#unsubscribing-from-the-mailing-list_1" title="Permanent link">¶</a></h2>
<p>To unsubscribe, send a message whose subject and body contains 'unsubscribe' to <a href="mailto:commits-unsubscribe@mina.apache.org">commits-unsubscribe@mina.apache.org</a> in plain text format will unsubscribe you from the mailing list though. You can actually send an empty or rich text message to unsubscribe, but our spam filter might reject your message</p>
-<h1 id="archive">Archive</h1>
+<h1 id="archive">Archive<a class="headerlink" href="#archive" title="Permanent link">¶</a></h1>
<p>All previous messages are archived in the following site:</p>
<ul>
<li><a href="http://www.nabble.com/Apache-MINA-f16868.html">Nabble.com</a></li>
Modified: websites/staging/mina/trunk/content/mina-project/codec-repo.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/codec-repo.html (original)
+++ websites/staging/mina/trunk/content/mina-project/codec-repo.html Tue Nov 10 08:41:53 2015
@@ -74,7 +74,18 @@
- <div id="navigation">
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<div id="navigation">
<h5>Latest Downloads</h5>
<ul>
@@ -139,15 +150,26 @@
-<h1 id="overview">Overview</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">¶</a></h1>
<p>This page captures known MINA Codecs available. These codecs may not be part of Apache MINA project. The Codecs are for reference purpose only.</p>
<DIV class="info" markdown="1">
The Codecs listed here may not be part of Apache MINA project. The information is for MINA Users for reference implementation available over the web
</DIV>
-<h2 id="protocol-codecs">Protocol Codecs</h2>
+<h2 id="protocol-codecs">Protocol Codecs<a class="headerlink" href="#protocol-codecs" title="Permanent link">¶</a></h2>
<p>The table below summarizes some of the known codecs</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Protocol</th>
Modified: websites/staging/mina/trunk/content/mina-project/conferences.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/conferences.html (original)
+++ websites/staging/mina/trunk/content/mina-project/conferences.html Tue Nov 10 08:41:53 2015
@@ -74,7 +74,18 @@
- <div id="navigation">
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<div id="navigation">
<h5>Latest Downloads</h5>
<ul>
@@ -139,7 +150,18 @@
-<h1 id="presentation-materials">Presentation Materials</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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="presentation-materials">Presentation Materials<a class="headerlink" href="#presentation-materials" title="Permanent link">¶</a></h1>
<p>These presentation materials will help you understand the overall architecture and core constructs of MINA.</p>
<ul>
<li><a href="../staticresources/pdfs/Mina_in_real_life_ASEU-2009.pdf">MINA in real life</a> (ApacheCon EU 2009) by Emmanuel Lécharny</li>
@@ -147,7 +169,7 @@
<li><a href="../staticresources/pdfs/ACUS2007.pdf">Apache MINA - The High Performance Protocol Construction Toolkit</a> (ApacheCon US 2007) by Peter Royal</li>
<li><a href="../staticresources/pdfs/ACAsia2006.pdf">Introduction to MINA (ApacheCon Asia 2006)</a> by Trustin Lee</li>
</ul>
-<h1 id="other-presentation-materials">Other Presentation Materials</h1>
+<h1 id="other-presentation-materials">Other Presentation Materials<a class="headerlink" href="#other-presentation-materials" title="Permanent link">¶</a></h1>
<ul>
<li><a href="../staticresources/pdfs/ACEU2007.pdf">Building TCP/IP Servers with Apache MINA</a> (ApacheCon EU 2007) by Peter Royal</li>
<li><a href="../staticresources/pdfs/ACEU2006.pdf">Building TCP/IP Servers with Apache MINA</a> (ApacheCon EU 2006) by Peter Royal</li>
Modified: websites/staging/mina/trunk/content/mina-project/developer-guide.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/developer-guide.html (original)
+++ websites/staging/mina/trunk/content/mina-project/developer-guide.html Tue Nov 10 08:41:53 2015
@@ -74,7 +74,18 @@
- <div id="navigation">
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<div id="navigation">
<h5>Latest Downloads</h5>
<ul>
@@ -139,7 +150,18 @@
-<h1 id="building-mina">Building MINA</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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-mina">Building MINA<a class="headerlink" href="#building-mina" title="Permanent link">¶</a></h1>
<DIV class="note" markdown="1">
Please read <a href="http://www.apache.org/dev/" class="external-link" rel="nofollow">the Developer Infrastructure Information</a> if you haven't yet before you proceed.
</DIV>
@@ -178,7 +200,7 @@
</li>
</ul>
</div>
-<h1 id="checking-out-the-code">Checking out the code</h1>
+<h1 id="checking-out-the-code">Checking out the code<a class="headerlink" href="#checking-out-the-code" title="Permanent link">¶</a></h1>
<p>You need Git to check out the source code from our source code repository, and [Maven(http://maven.apache.org/) 2.2.1 to build the source code (Building with Maven 3.0 will also work). The following example shows how to build the current stable branch (2.0.9).</p>
<div class="codehilite"><pre>$ <span class="n">git</span> <span class="n">clone</span> <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">git</span><span class="o">-</span><span class="n">wip</span><span class="o">-</span><span class="n">us</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="p">.</span><span class="n">git</span> <span class="n">mina</span>
$ <span class="n">cd</span> <span class="n">mina</span>
@@ -203,10 +225,10 @@ You can declare new variables in Eclipse
<p>For instance, to work on the on-going 2.0 version trunk, just do :</p>
<p>$ git clone http://git-wip-us.apache.org/repos/asf/mina.git mina
$ git checkout 2.0</p>
-<h1 id="coding-convention">Coding Convention</h1>
+<h1 id="coding-convention">Coding Convention<a class="headerlink" href="#coding-convention" title="Permanent link">¶</a></h1>
<p>We follow <a href="http://www.oracle.com/technetwork/java/javase/documentation/codeconvtoc-136057.html">Sun's standard Java coding convention</a> except that we always use spaces instead of tabs. Please download <a href="ImprovedJavaConventions.xml">the Eclipse Java formatter settings file</a> before you make any changes to the code.</p>
<p>This file is also available in the <code>/resources</code> directory.</p>
-<h1 id="class-header">Class header</h1>
+<h1 id="class-header">Class header<a class="headerlink" href="#class-header" title="Permanent link">¶</a></h1>
<p>As class header we use :</p>
<div class="codehilite"><pre><span class="cm">/** </span>
<span class="cm"> * Class desciption here.</span>
@@ -217,7 +239,7 @@ You can declare new variables in Eclipse
<p>The headers revisions tags are removed.</p>
-<h1 id="deploying-snapshots-commiters-only">Deploying Snapshots (Commiters Only)</h1>
+<h1 id="deploying-snapshots-commiters-only">Deploying Snapshots (Commiters Only)<a class="headerlink" href="#deploying-snapshots-commiters-only" title="Permanent link">¶</a></h1>
<p>Before running Maven to deploy artifacts, <em>please make sure if your umask is configured correctly</em>. Unless configured properly, other committers will experience annoying 'permission denied' errors. If your default shell is <code>bash</code>, please update your umask setting in the <code>~/.bashrc</code> file (create one if it doesn't exist.) by adding the following line:</p>
<div class="codehilite"><pre><span class="n">umask</span> 002
</pre></div>
@@ -232,8 +254,8 @@ $ <span class="n">mvn</span> <span class
<p>Please double-check the mode (i.e. <code>0664</code> or <code>-rw-rw-r--</code>, a.k.a permission code) of the deployed artifacts, otherwise you can waste other people's time significantly.</p>
-<h1 id="releasing-a-point-release-committers-only">Releasing a Point Release (Committers Only)</h1>
-<h2 id="preparing-the-release-for-the-vote">Preparing the release for the vote</h2>
+<h1 id="releasing-a-point-release-committers-only">Releasing a Point Release (Committers Only)<a class="headerlink" href="#releasing-a-point-release-committers-only" title="Permanent link">¶</a></h1>
+<h2 id="preparing-the-release-for-the-vote">Preparing the release for the vote<a class="headerlink" href="#preparing-the-release-for-the-vote" title="Permanent link">¶</a></h2>
<p>Before starting be sure to have the java and mvn command in your PATH.
On linux you can check with the following commands :</p>
<div class="codehilite"><pre>$ <span class="n">type</span> <span class="n">mvn</span>
@@ -243,13 +265,13 @@ $ <span class="n">type</span> <span clas
</pre></div>
-<h3 id="step-0-building-mina">Step 0: Building MINA</h3>
+<h3 id="step-0-building-mina">Step 0: Building MINA<a class="headerlink" href="#step-0-building-mina" title="Permanent link">¶</a></h3>
<p>As weird as it sounds, for some unknown reason (most certainly a misconfiguration in the Maven poms), we can't just run the release without having previously build all the projects. This is done with the following command :</p>
<div class="codehilite"><pre>$ <span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span> <span class="o">-</span><span class="n">Pserial</span>
</pre></div>
-<h3 id="step-1-tagging-and-deploying">Step 1: Tagging and Deploying</h3>
+<h3 id="step-1-tagging-and-deploying">Step 1: Tagging and Deploying<a class="headerlink" href="#step-1-tagging-and-deploying" title="Permanent link">¶</a></h3>
<p>First you need to configure maven for using the good username for scp and operation.</p>
<p>In the <code>~/.m2/settings.xml</code> you need the following lines :</p>
<div class="codehilite"><pre><span class="nt"><settings</span> <span class="na">xmlns=</span><span class="s">"http://maven.apache.org/POM/4.0.0"</span>
@@ -302,7 +324,7 @@ $ <span class="n">type</span> <span clas
</pre></div>
-<h3 id="step-2-processing-with-a-dry-run">step 2 : Processing with a dry run</h3>
+<h3 id="step-2-processing-with-a-dry-run">step 2 : Processing with a dry run<a class="headerlink" href="#step-2-processing-with-a-dry-run" title="Permanent link">¶</a></h3>
<p>After having checked out the trunk, and built it (see step 0), </p>
<div class="codehilite"><pre>$ <span class="n">git</span> <span class="n">clone</span> <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">git</span><span class="o">-</span><span class="n">wip</span><span class="o">-</span><span class="n">us</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="p">.</span><span class="n">git</span> <span class="n">mina</span>
$ <span class="n">cd</span> <span class="n">mina</span>
@@ -329,7 +351,7 @@ $ <span class="n">mvn</span> <span class
Make sure the change made by the release plugin is correct! (pom.xml, tags created)
</DIV>
-<h3 id="step-3-processing-with-the-real-release">Step 3 : Processing with the real release</h3>
+<h3 id="step-3-processing-with-the-real-release">Step 3 : Processing with the real release<a class="headerlink" href="#step-3-processing-with-the-real-release" title="Permanent link">¶</a></h3>
<p>When the dry run is successful, then you can do in real with the following commands:</p>
<div class="codehilite"><pre>$ <span class="n">mvn</span> <span class="o">-</span><span class="n">Pserial</span><span class="p">,</span><span class="n">apache</span><span class="o">-</span><span class="n">release</span> <span class="n">release</span><span class="p">:</span><span class="n">clean</span> # <span class="n">Clean</span> <span class="n">up</span> <span class="n">the</span> <span class="n">temporary</span> <span class="n">files</span> <span class="n">created</span> <span class="n">by</span> <span class="n">the</span> <span class="n">dry</span><span class="o">-</span><span class="n">run</span><span class="p">.</span>
$ <span class="n">mvn</span> <span class="o">-</span><span class="n">Pserial</span><span class="p">,</span><span class="n">apache</span><span class="o">-</span><span class="n">release</span> <span class="n">release</span><span class="p">:</span><span class="n">prepare</span> # <span class="n">Copy</span> <span class="n">to</span> <span class="n">tags</span> <span class="n">directory</span><span class="p">.</span>
@@ -346,7 +368,7 @@ $ <span class="n">mvn</span> <span class
<p>The first mail tells you that the SNAPSHOT has been moved to the release version in trunk, the second mails tells you that this version has been tagged, and the last mail tells you that trunk has moved to the next version.</p>
-<h3 id="step-4-perform-the-release">Step 4 : perform the release</h3>
+<h3 id="step-4-perform-the-release">Step 4 : perform the release<a class="headerlink" href="#step-4-perform-the-release" title="Permanent link">¶</a></h3>
<p>The last step before launching a vote is to push the potential release to Nexus so that every user can test the created packages. Perform the following actions</p>
<div class="codehilite"><pre>$ <span class="n">mvn</span> <span class="o">-</span><span class="n">Pserial</span><span class="p">,</span><span class="n">apache</span><span class="o">-</span><span class="n">release</span> <span class="n">release</span><span class="p">:</span><span class="n">perform</span>
<span class="p">...</span>
@@ -386,17 +408,17 @@ $ <span class="n">mvn</span> <span class
<p>Done !</p>
-<h3 id="step-5-closing-the-staging-release-on-nexus">Step 5 : closing the staging release on nexus</h3>
+<h3 id="step-5-closing-the-staging-release-on-nexus">Step 5 : closing the staging release on nexus<a class="headerlink" href="#step-5-closing-the-staging-release-on-nexus" title="Permanent link">¶</a></h3>
<p>Now, you have to close the staged project on nexus. In order to do that you <em>must</em> have exported your PGP key to a PGP public server <a href="http://www.apache.org/dev/openpgp.html">see</a></p>
<p>Connect to the Nexus server (https://repository.apache.org), login, and select the MINA staging repository you just created, then click on the 'close' button. You are home...</p>
-<h3 id="step-6-build-the-site">Step 6 : Build the Site</h3>
+<h3 id="step-6-build-the-site">Step 6 : Build the Site<a class="headerlink" href="#step-6-build-the-site" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre>$ <span class="n">cd</span> <span class="n">target</span><span class="o">/</span><span class="n">checkout</span>
$ <span class="n">mvn</span> <span class="o">-</span><span class="n">Pserial</span> <span class="n">site</span>
</pre></div>
<p>This creates the site.</p>
-<h3 id="step-7-sign-the-packages">Step 7 : Sign the packages</h3>
+<h3 id="step-7-sign-the-packages">Step 7 : Sign the packages<a class="headerlink" href="#step-7-sign-the-packages" title="Permanent link">¶</a></h3>
<p>Now, you have to sign the binary packages which are in target/checkout/distribution/target.</p>
<DIV class="note" markdown="1">
Use your PGP key ID (the pub key, 4096R/[XXXXXXX] where [XXXXXXX] is the key ID)
@@ -531,7 +553,7 @@ stty <span class="nb">echo</span>
</pre></div>
</td></tr></table>
-<h3 id="step-8-publish-source-and-binary-distribution-packages">Step 8 : Publish Source and Binary Distribution Packages</h3>
+<h3 id="step-8-publish-source-and-binary-distribution-packages">Step 8 : Publish Source and Binary Distribution Packages<a class="headerlink" href="#step-8-publish-source-and-binary-distribution-packages" title="Permanent link">¶</a></h3>
<p>First of all, create a new directory on people.apache.org/public_html to store the pacckages :</p>
<div class="codehilite"><pre>$ <span class="n">ssh</span> <span class="n">people</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span>
$ <span class="n">mkdir</span> <span class="n">public_html</span><span class="o">/</span><span class="n">mina</span><span class="o">-<</span><span class="n">version</span><span class="o">></span>
@@ -582,10 +604,10 @@ $ <span class="n">scp</span> <span class
</pre></div>
-<h3 id="step-9-test-the-new-version-with-ftpserver-sshd-and-vysper">Step 9 : Test the New Version with FtpServer, Sshd and Vysper</h3>
+<h3 id="step-9-test-the-new-version-with-ftpserver-sshd-and-vysper">Step 9 : Test the New Version with FtpServer, Sshd and Vysper<a class="headerlink" href="#step-9-test-the-new-version-with-ftpserver-sshd-and-vysper" title="Permanent link">¶</a></h3>
<p>In <em>FtpServer/pom.xml</em> change the <org.apache.directory.shared.version> property, build FtpServer. It should build with no error. Do the same thing with Sshd and Vysper.</p>
<p>It's time to launch a vote !</p>
-<h2 id="step-10-voting-a-release">Step 10 : Voting a release</h2>
+<h2 id="step-10-voting-a-release">Step 10 : Voting a release<a class="headerlink" href="#step-10-voting-a-release" title="Permanent link">¶</a></h2>
<p>Once the tarballs have been created, and the binaries available in Nexus, a vote can be launched. Simply send a mail on the dev@mina.apache.org mailing list describing the new release.</p>
<p>Here is how you send a [VOTE] mail on the dev mailing list :</p>
<div class="codehilite"><pre><span class="n">Hi</span><span class="p">,</span>
@@ -624,7 +646,7 @@ $ <span class="n">scp</span> <span class
<p>The vote will be open for 72 hours. Once the delay is over, collect the votes, and count the binding +1/-1. If the vote is positive, then we can release.</p>
-<h3 id="step-11-close-the-vote">Step 11 : Close the vote</h3>
+<h3 id="step-11-close-the-vote">Step 11 : Close the vote<a class="headerlink" href="#step-11-close-the-vote" title="Permanent link">¶</a></h3>
<p>You can officially close the vote now. There are some more steps to fulfill :</p>
<ul>
<li>Release the project on https://repository.apache.org</li>
@@ -644,7 +666,7 @@ $
</pre></div>
-<h3 id="step-12-deploy-web-reports-javadoc-and-jxr">Step 12: Deploy Web Reports (JavaDoc and JXR)</h3>
+<h3 id="step-12-deploy-web-reports-javadoc-and-jxr">Step 12: Deploy Web Reports (JavaDoc and JXR)<a class="headerlink" href="#step-12-deploy-web-reports-javadoc-and-jxr" title="Permanent link">¶</a></h3>
<p>The javadoc and xref files have been generated in step 6, it's now time to push them into the production site. They are generated in the following directory :</p>
<div class="codehilite"><pre><span class="n">target</span><span class="o">/</span><span class="n">checkout</span><span class="o">/</span><span class="n">target</span><span class="o">/</span><span class="n">site</span>
</pre></div>
@@ -699,13 +721,13 @@ $ <span class="n">vi</span> <span class=
</pre></div>
-<h3 id="step-13-wait-24-hours">Step 13: Wait 24 hours</h3>
+<h3 id="step-13-wait-24-hours">Step 13: Wait 24 hours<a class="headerlink" href="#step-13-wait-24-hours" title="Permanent link">¶</a></h3>
<p>We have to wait at least 24 hours for all mirrors to retrieve the uploaded files before making any announcement. I'd recommend you to wait for 48 hours because some mirrors might lag due to various issues.</p>
-<h3 id="step-14-update-the-links-in-web-site">Step 14: Update the Links in Web Site</h3>
+<h3 id="step-14-update-the-links-in-web-site">Step 14: Update the Links in Web Site<a class="headerlink" href="#step-14-update-the-links-in-web-site" title="Permanent link">¶</a></h3>
<p>Update the links to new distributions in [Downloads] page.</p>
-<h3 id="step-15-wait-another-24-hours">Step 15: Wait another 24 hours</h3>
+<h3 id="step-15-wait-another-24-hours">Step 15: Wait another 24 hours<a class="headerlink" href="#step-15-wait-another-24-hours" title="Permanent link">¶</a></h3>
<p>We need to wait until any changes made in the web site and metadata file(s) go live.</p>
-<h3 id="step-16-announce-the-new-release">Step 16: Announce the New Release</h3>
+<h3 id="step-16-announce-the-new-release">Step 16: Announce the New Release<a class="headerlink" href="#step-16-announce-the-new-release" title="Permanent link">¶</a></h3>
<p>An announcement message can be sent to [mailto:announce@apache.org], [mailto:announce@apachenews.org], [mailto:users@mina.apache.org] and [mailto:dev@mina.apache.org]. Please note that announcement messages are rejected unless your from-address ends with <code>@apache.org</code>. Plus, you shouldn't forget to post a news to the MINA site main page.</p>
Modified: websites/staging/mina/trunk/content/mina-project/documentation.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/documentation.html (original)
+++ websites/staging/mina/trunk/content/mina-project/documentation.html Tue Nov 10 08:41:53 2015
@@ -74,7 +74,18 @@
- <div id="navigation">
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<div id="navigation">
<h5>Latest Downloads</h5>
<ul>
@@ -139,7 +150,18 @@
-<h1 id="documentation">Documentation</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h1>
<DIV class="note" markdown="1">
The MINA 2.0 User Guide can be found here : [User Guide](userguide/user-guide-toc.html)
</DIV>
@@ -159,7 +181,7 @@ The MINA 2.0 User Guide can be found her
</li>
</ul>
</div>
-<h2 id="presentation-materials">Presentation Materials</h2>
+<h2 id="presentation-materials">Presentation Materials<a class="headerlink" href="#presentation-materials" title="Permanent link">¶</a></h2>
<p>These presentation materials will help you understand the overall architecture and core constructs of MINA</p>
<ul>
<li><a href="resources/Mina_in_real_life_ASEU-2009.pdf">MINA in real life (ApacheCon EU 2009)</a> by Emmanuel Lécharny</li>
@@ -167,9 +189,9 @@ The MINA 2.0 User Guide can be found her
<li><a href="resources/ACUS2007.pdf">Apache MINA - The High Performance Protocol Construction Toolkit (ApacheCon US 2007)</a> by Peter Royal</li>
<li><a href="resources/ACAsia2006.pdf">Introduction to MINA (ApacheCon Asia 2006)</a> by Trustin Lee</li>
</ul>
-<h2 id="versions-references">Versions & References</h2>
+<h2 id="versions-references">Versions & References<a class="headerlink" href="#versions-references" title="Permanent link">¶</a></h2>
<p>There are currently two branches in MINA:</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>JavaDoc</th>
@@ -191,7 +213,7 @@ The MINA 2.0 User Guide can be found her
</tbody>
</table>
<p>You might also want to read the [frequently asked questions](faq.html] and learn how to <a href="../contact.html">contact us</a> before getting started.</p>
-<h2 id="tutorials">Tutorials</h2>
+<h2 id="tutorials">Tutorials<a class="headerlink" href="#tutorials" title="Permanent link">¶</a></h2>
<ul>
<li><a href="quick-start-guide.html">MINA v2.0 Quick Start Guide</a> - Create your first MINA based program using MINA version 2.0</li>
<li><a href="userguide/ch12-logging-filter/ch12-logging-filter.html">Logging Configuration</a> - Configuring your MINA-based application for logging</li>
@@ -213,13 +235,13 @@ The MINA 2.0 User Guide can be found her
</li>
<li><a href="userguide/user-guide-toc.html">User Guide</a> - The new draft MINA User Guide.</li>
</ul>
-<h3 id="for-developers">For Developers</h3>
+<h3 id="for-developers">For Developers<a class="headerlink" href="#for-developers" title="Permanent link">¶</a></h3>
<ul>
<li><a href="developer-guide.html">Developer Guide</a> - Building & deploying MINA, Coding Standard, and more</li>
</ul>
-<h2 id="examples">Examples</h2>
+<h2 id="examples">Examples<a class="headerlink" href="#examples" title="Permanent link">¶</a></h2>
<p>You can browse all examples <a href="http://mina.apache.org/mina-project/xref/org/apache/mina/example/">here</a>.</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Name</th>
@@ -270,7 +292,7 @@ The MINA 2.0 User Guide can be found her
</tr>
</tbody>
</table>
-<h2 id="older-presentation-materials">Older Presentation Materials</h2>
+<h2 id="older-presentation-materials">Older Presentation Materials<a class="headerlink" href="#older-presentation-materials" title="Permanent link">¶</a></h2>
<ul>
<li><a href="resources/ACEU2007.pdf">Building TCP/IP Servers with Apache MINA (ApacheCon EU 2007)</a> by Peter Royal</li>
<li><a href="resources/ACEU2006.pdf">Building TCP/IP Servers with Apache MINA (ApacheCon EU 2006)</a> by Peter Royal</li>
Modified: websites/staging/mina/trunk/content/mina-project/faq.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/faq.html (original)
+++ websites/staging/mina/trunk/content/mina-project/faq.html Tue Nov 10 08:41:53 2015
@@ -74,7 +74,18 @@
- <div id="navigation">
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<div id="navigation">
<h5>Latest Downloads</h5>
<ul>
@@ -139,6 +150,17 @@
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>MINA FAQ</H1>
<div class="toc">
@@ -174,11 +196,11 @@
</ul>
</li>
<li><a href="#troubleshooting">Troubleshooting</a><ul>
-<li><a href="#i-get-wzxhzdk27outofmemoryerrorwzxhzdk28-or-response-timeout-and-connection-reset-under-heavy-load">I get <TT>OutOfMemoryError</TT> or response timeout and connection reset under heavy load.</a></li>
+<li><a href="#i-get-outofmemoryerror-or-response-timeout-and-connection-reset-under-heavy-load">I get <TT>OutOfMemoryError</TT> or response timeout and connection reset under heavy load.</a></li>
<li><a href="#no-data-is-writtin-out-to-the-session-even-if-the-buffer-is-not-empty">No data is writtin out to the session even if the buffer is not empty.</a></li>
<li><a href="#i-created-an-ssl-client-with-mina-but-it-doesnt-initiate-any-handshake-after-the-session-is-open">I created an SSL client with MINA, but it doesn't initiate any handshake after the session is open.</a></li>
<li><a href="#why-does-socketconnector-send-several-messages-as-one-message">Why does SocketConnector send several messages as one message?</a></li>
-<li><a href="#i-get-wzxhzdk31invalidclasschangeerrorwzxhzdk32">I get <TT>InvalidClassChangeError</TT>.</a></li>
+<li><a href="#i-get-invalidclasschangeerror">I get <TT>InvalidClassChangeError</TT>.</a></li>
<li><a href="#my-server-fails-with-javanetsocketexception-too-many-files-open">My server fails with java.net.SocketException: Too many files open<</a><ul>
<li><a href="#change-the-timeout-in-windows">Change the timeout in Windows</a></li>
<li><a href="#change-the-timeout-in-linux">Change the timeout in Linux</a></li>
@@ -190,7 +212,7 @@
</div>
<H2>General</H2>
-<h2 id="what-does-mina-mean">What does MINA mean?</h2>
+<h2 id="what-does-mina-mean">What does MINA mean?<a class="headerlink" href="#what-does-mina-mean" title="Permanent link">¶</a></h2>
<p>MINA is:</p>
<ul>
<li>An acronym for 'Multipurpose Infrastructure for Network Applications';</li>
@@ -199,44 +221,44 @@
<li>'Mine' (as in mineshaft) in Spanish and Portuguese;</li>
<li>Look at <a href="http://en.wikipedia.org/wiki/Mina">Wikipedia</a> for more meanings.</li>
</ul>
-<h3 id="what-transport-does-mina-support">What transport does MINA support?</h3>
+<h3 id="what-transport-does-mina-support">What transport does MINA support?<a class="headerlink" href="#what-transport-does-mina-support" title="Permanent link">¶</a></h3>
<p>MINA currently supports TCP and UDP based on Java NIO API, provides support for serial port communication, and transports based on <a href="http://apr.apache.org/">Apache Portable Runtime</a>.</p>
-<h3 id="how-does-mina-perform">How does MINA perform?</h3>
+<h3 id="how-does-mina-perform">How does MINA perform?<a class="headerlink" href="#how-does-mina-perform" title="Permanent link">¶</a></h3>
<p>It is known to perform as good as C/C++ servers. Please refer to the <A href="performances.html" title="Performance Test Reports">Performance Test Reports</A> or the <A href="testimonials.html" title="Testimonials">Testimonials</A>.</p>
-<h3 id="which-version-of-mina-should-i-use">Which version of MINA should I use?</h3>
+<h3 id="which-version-of-mina-should-i-use">Which version of MINA should I use?<a class="headerlink" href="#which-version-of-mina-should-i-use" title="Permanent link">¶</a></h3>
<p>Use the latest point-release of 2.0 (for Java 5 or above). 1.0 and 1.1 aren't maintained anymore.</p>
-<h3 id="what-is-required-to-buildrun-mina">What is required to build/run MINA?</h3>
+<h3 id="what-is-required-to-buildrun-mina">What is required to build/run MINA?<a class="headerlink" href="#what-is-required-to-buildrun-mina" title="Permanent link">¶</a></h3>
<p>JDK 1.5 or above is required to build MINA. But MINA runs perfect with JDK 1.4 only if you don't use SSLFilter which uses Java 5 SSLEngine. This means JDK 1.5 or above is required for you to use SSL with MINA.</p>
<p>MINA core module depends on two libraries, SLF4J and backport-util-concurrent (for 1.0):</p>
<p><a href="http://www.slf4j.org/">SLF4J (Simple Logging Facade for Java)</a></A>, a logging framework from the author of <a href="http://logging.apache.org/log4j/1.2/index.html">Log4J</a>. SLF4J is very similar to <a href="http://jakarta.apache.org/commons/logging/">Commons-Logging</a>, but it doesn't cause any class loader issues at all. SLF4J provides bindings for Log4J, JDK 1.4 logging API, and NLog4J. Please put an appropriate SLF4J JAR file which corresponds to your favorite logging framework to the classpath as SLF4J documentation explains.</p>
<p><a href="http://www.springframework.org/">Spring framework</a> and <a href="http://www.jcraft.com/jzlib/">JZlib</a> are also required to build <TT>integration-spring</TT> and <TT>filter-compression</TT> module.</p>
-<h3 id="how-can-i-get-help">How can I get help?</h3>
+<h3 id="how-can-i-get-help">How can I get help?<a class="headerlink" href="#how-can-i-get-help" title="Permanent link">¶</a></h3>
<p>The primary source to get help is the <a href="userguide/user-guide-toc.html">User Guide</a>. You can also contact us via <a href="../contact.html">various channels</a> to ask questions on MINA or to contribute to it.</p>
-<h3 id="how-what-can-i-contribute">How / What can I contribute?</h3>
+<h3 id="how-what-can-i-contribute">How / What can I contribute?<a class="headerlink" href="#how-what-can-i-contribute" title="Permanent link">¶</a></h3>
<p>You can contribute anything related with MINA; examples, useful codecs for existing protocols, tutorials, feature improvements, bug fixes, benchmarks, and whatever. Please <a href="../contact.html">contact us</a> without hesitation.</p>
-<h2 id="can-mina">Can MINA...?</h2>
-<h3 id="can-i-use-mina-to-create-client-or-server-applications">Can I use MINA to create client (or server) applications?</h3>
+<h2 id="can-mina">Can MINA...?<a class="headerlink" href="#can-mina" title="Permanent link">¶</a></h2>
+<h3 id="can-i-use-mina-to-create-client-or-server-applications">Can I use MINA to create client (or server) applications?<a class="headerlink" href="#can-i-use-mina-to-create-client-or-server-applications" title="Permanent link">¶</a></h3>
<p>Yes. You can create both client and server applications with MINA. Please take a look at <TT>IoConnector</TT> and <TT>IoAcceptor</TT>.</p>
-<h3 id="can-mina-handle-text-protocols-such-as-http">Can MINA handle text protocols such as HTTP?</h3>
+<h3 id="can-mina-handle-text-protocols-such-as-http">Can MINA handle text protocols such as HTTP?<a class="headerlink" href="#can-mina-handle-text-protocols-such-as-http" title="Permanent link">¶</a></h3>
<p>Yes. Please take a look at <a href="documentation.html">the Reversed and HTTP server examples</a>. AsyncWeb](asyncweb.html)</A> is a HTTP server implementation based on MINA.</p>
-<h3 id="can-mina-handle-complex-binary-protocols-such-as-ldap">Can MINA handle complex binary protocols such as LDAP?</h3>
+<h3 id="can-mina-handle-complex-binary-protocols-such-as-ldap">Can MINA handle complex binary protocols such as LDAP?<a class="headerlink" href="#can-mina-handle-complex-binary-protocols-such-as-ldap" title="Permanent link">¶</a></h3>
<p>Yes. Please take a look at <a href="documentation.html">the SumUp example</a>. There is no full ASN.1 support yet, but we will implement it someday and you can contribute to make it available sooner.</p>
-<h3 id="can-i-implement-protocols-that-keeps-connection-alive-with-mina">Can I implement protocols that keeps connection alive with MINA?</h3>
+<h3 id="can-i-implement-protocols-that-keeps-connection-alive-with-mina">Can I implement protocols that keeps connection alive with MINA?<a class="headerlink" href="#can-i-implement-protocols-that-keeps-connection-alive-with-mina" title="Permanent link">¶</a></h3>
<p>Yes. MINA doesn't close any connections unless you called <code>IoSession.close()</code> or connection is closed by the remote peer.</p>
-<h3 id="does-mina-support-ssltls-and-sasl-out-of-the-box">Does MINA support SSL/TLS and SASL out-of-the-box?</h3>
+<h3 id="does-mina-support-ssltls-and-sasl-out-of-the-box">Does MINA support SSL/TLS and SASL out-of-the-box?<a class="headerlink" href="#does-mina-support-ssltls-and-sasl-out-of-the-box" title="Permanent link">¶</a></h3>
<p>We support SSL/TLS out-of-the-box. Please refer to <code>SSLFilter</code>. It also provides a way to implement <TT>StartTLS</TT>. JDK 1.5 provides complete SASL support which works well with MINA.</p>
-<h3 id="do-i-need-to-make-my-iohandler-thread-safe">Do I need to make my IoHandler thread-safe?</h3>
+<h3 id="do-i-need-to-make-my-iohandler-thread-safe">Do I need to make my IoHandler thread-safe?<a class="headerlink" href="#do-i-need-to-make-my-iohandler-thread-safe" title="Permanent link">¶</a></h3>
<p>It depends on your implementation. If you access the resource which is shared across multiple sessions, you have to make it thread-safe. If the resource is not shared at all and accessed by only one session (e.g. storing context information as a session attribute), then you don't need to make it thread-safe. It is because all events generated by MINA are transmitted to your handler in order (when using the Executor Filter), and the newer event is not processed if the event handler method for the older event for the same session hasn't returned yet.</p>
-<h3 id="what-transport-types-can-mina-support-except-tcpip-and-udpip">What transport types can MINA support except TCP/IP and UDP/IP?</h3>
+<h3 id="what-transport-types-can-mina-support-except-tcpip-and-udpip">What transport types can MINA support except TCP/IP and UDP/IP?<a class="headerlink" href="#what-transport-types-can-mina-support-except-tcpip-and-udpip" title="Permanent link">¶</a></h3>
<p>Virtually all kind of transport types. MINA API is designed to be transport-independent. You can implement any transport type support only if you can conform to MINA API. Support for Pre-1.4 I/O (aka BIO), reliable multicast, Java Communications API, and file I/O are planned.</p>
-<h3 id="does-mina-support-multicast">Does MINA support multicast?</h3>
+<h3 id="does-mina-support-multicast">Does MINA support multicast?<a class="headerlink" href="#does-mina-support-multicast" title="Permanent link">¶</a></h3>
<p>Not yet. Java NIO doesn't support multicast yet. Multicast for NIO will be available in Java SE 7, Dolphin. We are seriously considering to implement multicasts using pre-1.4 Java API.</p>
-<h2 id="how-do-i">How do I...?</h2>
-<h3 id="how-can-i-store-session-specific-information">How can I store session-specific information?</h3>
+<h2 id="how-do-i">How do I...?<a class="headerlink" href="#how-do-i" title="Permanent link">¶</a></h2>
+<h3 id="how-can-i-store-session-specific-information">How can I store session-specific information?<a class="headerlink" href="#how-can-i-store-session-specific-information" title="Permanent link">¶</a></h3>
<p>Sessions are capable of custom attributes that you can add or remove at any time. These custom attributes are not shared between sessions; it is designed to store session specific information.</p>
-<h3 id="how-can-i-separate-an-event-handler-into-multiple-handlers-when-i-implement-complex-business-logic">How can I separate an event handler into multiple handlers when I implement complex business logic?</h3>
+<h3 id="how-can-i-separate-an-event-handler-into-multiple-handlers-when-i-implement-complex-business-logic">How can I separate an event handler into multiple handlers when I implement complex business logic?<a class="headerlink" href="#how-can-i-separate-an-event-handler-into-multiple-handlers-when-i-implement-complex-business-logic" title="Permanent link">¶</a></h3>
<p>Please refer to <TT>DemuxingIoHandler</TT>.</p>
-<h3 id="how-do-i-close-my-sessions-and-dispose-my-connector">How do I close my sessions and dispose my Connector?</h3>
+<h3 id="how-do-i-close-my-sessions-and-dispose-my-connector">How do I close my sessions and dispose my Connector?<a class="headerlink" href="#how-do-i-close-my-sessions-and-dispose-my-connector" title="Permanent link">¶</a></h3>
<p>You have to do it in two steps : first close your sessions, then dispose the connector. Of course, if you dispose your Connector first, then all the sessions will be closed. Here is the code :</p>
<div class="codehilite"><pre><span class="n">ConnectFuture</span> <span class="n">cf</span> <span class="o">=</span> <span class="n">connector</span><span class="o">.</span><span class="na">connect</span><span class="o">(</span><span class="k">new</span> <span class="n">InetSocketAddress</span><span class="o">(</span><span class="s">"localhost"</span><span class="o">,</span> <span class="mi">8080</span><span class="o">));</span>
@@ -263,7 +285,7 @@
</pre></div>
-<h3 id="how-can-i-reconnect-to-server-after-my-client-session-is-closed">How can I reconnect to server after my client session is closed?</h3>
+<h3 id="how-can-i-reconnect-to-server-after-my-client-session-is-closed">How can I reconnect to server after my client session is closed?<a class="headerlink" href="#how-can-i-reconnect-to-server-after-my-client-session-is-closed" title="Permanent link">¶</a></h3>
<p>Here is an example code:</p>
<div class="codehilite"><pre><span class="kd">public</span> <span class="kt">void</span> <span class="nf">sessionClosed</span><span class="o">(</span> <span class="n">IoSession</span> <span class="n">session</span> <span class="o">)</span> <span class="kd">throws</span> <span class="n">Exception</span> <span class="o">{</span>
<span class="c1">// Wait for five seconds before reconnecting.</span>
@@ -276,14 +298,14 @@
<p>Possibly it would be better to extract this code to a method like <code>reconnect()</code> so that it can reusable in more than one place.</p>
-<h3 id="when-should-i-implement-my-protocol-handler-using-filters">When should I implement my protocol handler using filters?</h3>
+<h3 id="when-should-i-implement-my-protocol-handler-using-filters">When should I implement my protocol handler using filters?<a class="headerlink" href="#when-should-i-implement-my-protocol-handler-using-filters" title="Permanent link">¶</a></h3>
<p><code>IoFilter</code> is usually considered reusable just like we think about Servlet filters. Please implement commonly used business logic such as authorization and logging as a filter. In case you implement just complex multi-layer protocols like Kerberos, you could consider using <code>org.apache.mina.handler.chain</code>> package.</p>
-<h3 id="how-can-i-detect-when-the-remote-peer-doesnt-send-a-response-message-for-my-request-message">How can I detect when the remote peer doesn't send a response message for my request message?</h3>
+<h3 id="how-can-i-detect-when-the-remote-peer-doesnt-send-a-response-message-for-my-request-message">How can I detect when the remote peer doesn't send a response message for my request message?<a class="headerlink" href="#how-can-i-detect-when-the-remote-peer-doesnt-send-a-response-message-for-my-request-message" title="Permanent link">¶</a></h3>
<p>You can't use <code>sessionIdle</code> event simply here. You'll have to use <code>java.util.concurrent.ScheduledExecutor</code> (or <a href="http://www.opensymphony.com/quartz/">OpenSymphony Quartz</a> as an alternative). Schedule a timeout task to be executed on timeout situation for each request message, and cancel it when you receive the corresponding response message.</p>
-<h3 id="how-can-i-let-mina-log-messages-using-my-favorite-logging-framework-ie-log4j">How can I let MINA log messages using my favorite logging framework (i.e. Log4J)?</h3>
+<h3 id="how-can-i-let-mina-log-messages-using-my-favorite-logging-framework-ie-log4j">How can I let MINA log messages using my favorite logging framework (i.e. Log4J)?<a class="headerlink" href="#how-can-i-let-mina-log-messages-using-my-favorite-logging-framework-ie-log4j" title="Permanent link">¶</a></h3>
<p>Please refer to 'Swapping implementations at deployment time' section in <a href="http://www.slf4j.org/manual.html">the SLF4J Manual</a>.</p>
-<h2 id="troubleshooting">Troubleshooting</h2>
-<h3 id="i-get-wzxhzdk27outofmemoryerrorwzxhzdk28-or-response-timeout-and-connection-reset-under-heavy-load">I get <TT>OutOfMemoryError</TT> or response timeout and connection reset under heavy load.</h3>
+<h2 id="troubleshooting">Troubleshooting<a class="headerlink" href="#troubleshooting" title="Permanent link">¶</a></h2>
+<h3 id="i-get-outofmemoryerror-or-response-timeout-and-connection-reset-under-heavy-load">I get <TT>OutOfMemoryError</TT> or response timeout and connection reset under heavy load.<a class="headerlink" href="#i-get-outofmemoryerror-or-response-timeout-and-connection-reset-under-heavy-load" title="Permanent link">¶</a></h3>
<p>We recommend to switch the default buffer type to 'heap' by inserting the following code before you start a server:</p>
<div class="codehilite"><pre><span class="n">ByteBuffer</span><span class="p">.</span><span class="n">setUseDirectBuffers</span><span class="p">(</span><span class="n">false</span><span class="p">);</span>
<span class="n">ByteBuffer</span><span class="p">.</span><span class="n">setAllocator</span><span class="p">(</span><span class="n">new</span> <span class="n">SimpleByteBufferAllocator</span><span class="p">());</span>
@@ -291,11 +313,11 @@
<p>If you prefer direct buffers to heap buffers, JVM might have ran out of direct memory. Please try increasing maximum direct memory size using <strong>-XX:MaxDirectMemorySize</strong> option (e.g. <strong>-XX:MaxDirectMemorySize=128M</strong>)</p>
-<h3 id="no-data-is-writtin-out-to-the-session-even-if-the-buffer-is-not-empty">No data is writtin out to the session even if the buffer is not empty.</h3>
+<h3 id="no-data-is-writtin-out-to-the-session-even-if-the-buffer-is-not-empty">No data is writtin out to the session even if the buffer is not empty.<a class="headerlink" href="#no-data-is-writtin-out-to-the-session-even-if-the-buffer-is-not-empty" title="Permanent link">¶</a></h3>
<p>Please make sure if you called <code>ByteBuffer.flip()</code> to flip the buffer before writing the buffer out. It is a common mistake NIO beginners make.</p>
-<h3 id="i-created-an-ssl-client-with-mina-but-it-doesnt-initiate-any-handshake-after-the-session-is-open">I created an SSL client with MINA, but it doesn't initiate any handshake after the session is open.</h3>
+<h3 id="i-created-an-ssl-client-with-mina-but-it-doesnt-initiate-any-handshake-after-the-session-is-open">I created an SSL client with MINA, but it doesn't initiate any handshake after the session is open.<a class="headerlink" href="#i-created-an-ssl-client-with-mina-but-it-doesnt-initiate-any-handshake-after-the-session-is-open" title="Permanent link">¶</a></h3>
<p>Please make sure you called <code>SSLFilter.setUseClientMode(true)</code> before you initiate a connection. Server developers will also have to disconnect users who doesn't initiate SSL handshake by setting <code>IoSession.readerIdleTime</code> and closing the session in <code>IoHandler.sessionIdle()</code>.</p>
-<h3 id="why-does-socketconnector-send-several-messages-as-one-message">Why does SocketConnector send several messages as one message?</h3>
+<h3 id="why-does-socketconnector-send-several-messages-as-one-message">Why does SocketConnector send several messages as one message?<a class="headerlink" href="#why-does-socketconnector-send-several-messages-as-one-message" title="Permanent link">¶</a></h3>
<p><em>For example, I tried using SocketConnector to send "abc" and "def", but it sent "abcdef". Is it a MINA bug?</em></p>
<p>No, this is due to your OS trying to send packets more efficiently (see <a href="http://en.wikipedia.org/wiki/Nagle_algorithm">Nagle algorithm</a>). You can enable/disable Nagle's algorithm by a call to SocketSessionConfig.setTcpNoDelay(), e.g.:</p>
<div class="codehilite"><pre><span class="o">((</span><span class="n">SocketSessionConfig</span><span class="o">)</span> <span class="n">connector</span><span class="o">.</span><span class="na">getSessionConfig</span><span class="o">()).</span><span class="na">setTcpNoDelay</span><span class="o">(</span><span class="kc">false</span><span class="o">)</span>
@@ -303,18 +325,18 @@
<p>However, even if you do this you cannot expect one session.write(bytes) in MINA to correspond to one TCP packet on your network. You should probably implement your own MINA ProtocolDecoder to handle the assembly of incoming bytes into message objects. The TextLineCodec is a good start if the protocol you're implementing is based on text lines. For a more advanced example have a look at the SumUp example in the MINA distribution.</p>
-<h3 id="i-get-wzxhzdk31invalidclasschangeerrorwzxhzdk32">I get <TT>InvalidClassChangeError</TT>.</h3>
+<h3 id="i-get-invalidclasschangeerror">I get <TT>InvalidClassChangeError</TT>.<a class="headerlink" href="#i-get-invalidclasschangeerror" title="Permanent link">¶</a></h3>
<p>Please make sure if you are using the appropriate SLF4J version. You will get <code>InvalidClassChangeError</code> if you are using outdated SLF4J release.</p>
-<h3 id="my-server-fails-with-javanetsocketexception-too-many-files-open">My server fails with java.net.SocketException: Too many files open<</h3>
+<h3 id="my-server-fails-with-javanetsocketexception-too-many-files-open">My server fails with java.net.SocketException: Too many files open<<a class="headerlink" href="#my-server-fails-with-javanetsocketexception-too-many-files-open" title="Permanent link">¶</a></h3>
<p>Network sockets are treated like files and your operating system has a limit to the number of file handles it can manage. Running out of file handles is usually due to a large number of clients connecting and disconnecting frequently. As specified by TCP, after being closed sockets remain in the TIME_WAIT state for some additional time. The reason is to ensure that delayed packets arrive on the correct socket. In Windows, the default TIME_WAIT timeout is 4 minutes, in Linux it is 60 seconds.</p>
-<h4 id="change-the-timeout-in-windows">Change the timeout in Windows</h4>
+<h4 id="change-the-timeout-in-windows">Change the timeout in Windows<a class="headerlink" href="#change-the-timeout-in-windows" title="Permanent link">¶</a></h4>
<ol>
<li>Run regedit to start the Registry Editor</li>
<li>Locate the following key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\tcpip\Parameters</li>
<li>Add a new value named TcpTimedWaitDelay asa decimal and set the desired timeout in seconds (30-300)</li>
<li>Reboot</li>
</ol>
-<h4 id="change-the-timeout-in-linux">Change the timeout in Linux</h4>
+<h4 id="change-the-timeout-in-linux">Change the timeout in Linux<a class="headerlink" href="#change-the-timeout-in-linux" title="Permanent link">¶</a></h4>
<ol>
<li>
<p>Update the configuration value by running (30 seconds used in the example)</LI></p>
Modified: websites/staging/mina/trunk/content/mina-project/features.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/features.html (original)
+++ websites/staging/mina/trunk/content/mina-project/features.html Tue Nov 10 08:41:53 2015
@@ -74,7 +74,18 @@
- <div id="navigation">
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<div id="navigation">
<h5>Latest Downloads</h5>
<ul>
@@ -139,11 +150,22 @@
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
<div class="codehilite"><pre>
</pre></div>
-<h1 id="features">Features</h1>
+<h1 id="features">Features<a class="headerlink" href="#features" title="Permanent link">¶</a></h1>
<p>MINA is a simple yet full-featured network application framework which provides:</p>
<ul>
<li>Unified API for various transport types:<ul>
Modified: websites/staging/mina/trunk/content/mina-project/index.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/index.html (original)
+++ websites/staging/mina/trunk/content/mina-project/index.html Tue Nov 10 08:41:53 2015
@@ -74,7 +74,18 @@
- <div id="navigation">
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<div id="navigation">
<h5>Latest Downloads</h5>
<ul>
@@ -140,8 +151,19 @@
- <h1 id="welcome-to-apache-mina">Welcome to Apache MINA</h1>
-<h2 id="overview">Overview</h2>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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="welcome-to-apache-mina">Welcome to Apache MINA<a class="headerlink" href="#welcome-to-apache-mina" title="Permanent link">¶</a></h1>
+<h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">¶</a></h2>
<p>Apache <abbr title="Multipurpose Infrastructure for Network Applications">MINA</abbr> is a network application framework which helps users develop high performance and high scalability network applications easily. It provides an abstract ·event-driven · asynchronous API over various transports such as TCP/IP and UDP/IP via Java NIO.</p>
<p>Apache MINA is often called:</p>
<ul>
@@ -152,7 +174,18 @@
<p>However, it's much more than that. Please take a look around the list of the <em><a href="features.html">features</a></em> that enable rapid network application development, and <em><a href="testimonials.html">what people says about MINA</a></em>. </p>
<p>Please grab yourself a <em><a href="downloads.html">download</a></em>, try our <em><a href="quick-start-guide.html">Quick Start Guide</a></em>, surf our <em><a href="faq.html">FAQ</a></em> or start join us on <em><a href="../contact.html">our community</a></em></p>
- <div class="news"><p>Notice: Licensed to the Apache Software Foundation (ASF) under one
+ <div class="news"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<p>Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
@@ -168,8 +201,8 @@
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.</p>
-<h1 id="news">News</h1>
-<h2 id="mina-209-released-posted-on-october-25-2014">MINA 2.0.9 released <em>posted on October, 25, 2014</em></h2>
+<h1 id="news">News<a class="headerlink" href="#news" title="Permanent link">¶</a></h1>
+<h2 id="mina-209-released-posted-on-october-25-2014">MINA 2.0.9 released <em>posted on October, 25, 2014</em><a class="headerlink" href="#mina-209-released-posted-on-october-25-2014" title="Permanent link">¶</a></h2>
<p>This new release of MINA is hust a bug fix release. A few issues have been fixed, one critical, inducing a 100% CPU, and one was annoying as it was generating stack traces for nothing.</p>
<p>You can check the list of fixes for this version there :</p>
<p><a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20DIRMINA%20AND%20fixVersion%20%3D%202.0.9%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC">Release note</a></p>
@@ -180,13 +213,13 @@
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-990">DIRMINA-990</a> - Control flow over exceptional path in AbstractIoBuffer</li>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-991">DIRMINA-991</a> - Possible faster deserialization in AbstractIoBuffer object deserialization.</li>
</ul>
-<h2 id="mina-208-released-posted-on-september-22-2014">MINA 2.0.8 released <em>posted on September, 22, 2014</em></h2>
+<h2 id="mina-208-released-posted-on-september-22-2014">MINA 2.0.8 released <em>posted on September, 22, 2014</em><a class="headerlink" href="#mina-208-released-posted-on-september-22-2014" title="Permanent link">¶</a></h2>
<p>It's 2 years we haven't had a release of MINA 2.0, it's about time.</p>
<p>We have tried to fix as much issues as we could in the last 3 weeks. As a result, we have closed around 90 JIRAs (fixed, postponed or simply discarded).</p>
<p>There is one change that might break the build for those switching from MINA 2.0.7 to MINA 2.0.8 : the <em>IoHandler</em> interface now has a method called <em>inputClosed()</em>, so either you have to implement this method if you are directly implementing the <em>IoHandler</em> interface, or better, you can extends <em>IoHandlerAdapter</em>, which implements a placeholder for this method.</p>
<p>You can check the list of fixes for this version there :</p>
<p><a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20DIRMINA%20AND%20fixVersion%20%3D%202.0.8%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC">Release note</a></p>
-<h3 id="bug">Bug</h3>
+<h3 id="bug">Bug<a class="headerlink" href="#bug" title="Permanent link">¶</a></h3>
<ul>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-539">DIRMINA-539</a> - NioDatagramConnector doesn't takes the TrafficClass value set to his DatagramSessionConfig</li>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-574">DIRMINA-574</a> - ClassCastException when a message is written on a closed session.</li>
@@ -244,7 +277,7 @@
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-982">DIRMINA-982</a> - ProtocolEncoderOutputImpl.flush() throws an IllegalArgumentException if buffers queue is empty</li>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-983">DIRMINA-983</a> - Problems with TextLineDecoder and special characters</li>
</ul>
-<h3 id="improvement">Improvement</h3>
+<h3 id="improvement">Improvement<a class="headerlink" href="#improvement" title="Permanent link">¶</a></h3>
<ul>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-210">DIRMINA-210</a> - Investigate removal of static methods in ByteBuffer</li>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-237">DIRMINA-237</a> - Improve Spring integration</li>
@@ -271,7 +304,7 @@
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-941">DIRMINA-941</a> - DefaultIoFilterChain (or any other class) should not catch Throwable without re-throwing</li>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-945">DIRMINA-945</a> - DefaultVmPipeSessionConfig is empty</li>
</ul>
-<h3 id="new-feature">New Feature</h3>
+<h3 id="new-feature">New Feature<a class="headerlink" href="#new-feature" title="Permanent link">¶</a></h3>
<ul>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-23">DIRMINA-23</a> - New transport type: non-NIO sockets</li>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-68">DIRMINA-68</a> - Automatic reconnect configuration for client channels.</li>
@@ -285,33 +318,33 @@
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-816">DIRMINA-816</a> - NioSocketConnector missing defaultLocalAddress</li>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-964">DIRMINA-964</a> - Custom NIO SelectorProvider for NioSocketAcceptor</li>
</ul>
-<h3 id="task">Task</h3>
+<h3 id="task">Task<a class="headerlink" href="#task" title="Permanent link">¶</a></h3>
<ul>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-56">DIRMINA-56</a> - Create a Benchmark Suite That Generates HTML Reports.</li>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-188">DIRMINA-188</a> - All-in-one JAR</li>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-477">DIRMINA-477</a> - Update page about differences between 1.x and 2.x</li>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-721">DIRMINA-721</a> - Get rid of multiton iohandler and netty2 codec as proposed on ML</li>
</ul>
-<h3 id="test">Test</h3>
+<h3 id="test">Test<a class="headerlink" href="#test" title="Permanent link">¶</a></h3>
<ul>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-922">DIRMINA-922</a> - Add a benchmark project to compare with other IO frameworks</li>
</ul>
-<h3 id="wish">Wish</h3>
+<h3 id="wish">Wish<a class="headerlink" href="#wish" title="Permanent link">¶</a></h3>
<ul>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-250">DIRMINA-250</a> - Provide a test suite for a transport implementor.</li>
<li><a href="https://issues.apache.org/jira/browse/DIRMINA-916">DIRMINA-916</a> - Adding Http Status code 101 "101 Switching Protocols" in org.apache.mina.http.api.HttpStatus</li>
</ul>
-<h2 id="mina-207-released-posted-on-october-12-2012">MINA 2.0.7 released <em>posted on October, 12, 2012</em></h2>
+<h2 id="mina-207-released-posted-on-october-12-2012">MINA 2.0.7 released <em>posted on October, 12, 2012</em><a class="headerlink" href="#mina-207-released-posted-on-october-12-2012" title="Permanent link">¶</a></h2>
<p>The Apache MINA project is pleased to announce MINA 2.0.7 ! This version is a bug fix release.</p>
<p>It fixes a regression introduced in MINA 2.0.5, and some performance improvements for the UDP server.</p>
<p>We recommend all users to upgrade to this release. We consider this a stable and production ready release.</p>
<p><a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10670&version=12323341">Release note1</a>
<a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10670&version=12316652">Release note2</a></p>
-<h2 id="mina-205-released-posted-on-august-26-2012">MINA 2.0.5 released <em>posted on August, 26, 2012</em></h2>
+<h2 id="mina-205-released-posted-on-august-26-2012">MINA 2.0.5 released <em>posted on August, 26, 2012</em><a class="headerlink" href="#mina-205-released-posted-on-august-26-2012" title="Permanent link">¶</a></h2>
<p>The Apache MINA project is pleased to announce MINA 2.0.5 ! This version is a bug fix release.</p>
<p>We recommend all users to upgrade to this release. We consider this a stable and production ready release.</p>
<p><a href="http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10670&version=12316474">Release note</a></p>
-<h2 id="mina-204-released-posted-on-august-26-2012">MINA 2.0.4 released <em>posted on August, 26, 2012</em></h2>
+<h2 id="mina-204-released-posted-on-august-26-2012">MINA 2.0.4 released <em>posted on August, 26, 2012</em><a class="headerlink" href="#mina-204-released-posted-on-august-26-2012" title="Permanent link">¶</a></h2>
<p>The Apache MINA project is pleased to announce MINA 2.0.4 ! This version is a bug fix release.</p>
<p>We recommend all users to upgrade to this release. We consider this a stable and production ready release.</p>
<p><a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10670&version=12316009">Release note</a></p></div>
Modified: websites/staging/mina/trunk/content/mina-project/issue-tracking.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/issue-tracking.html (original)
+++ websites/staging/mina/trunk/content/mina-project/issue-tracking.html Tue Nov 10 08:41:53 2015
@@ -74,7 +74,18 @@
- <div id="navigation">
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<div id="navigation">
<h5>Latest Downloads</h5>
<ul>
@@ -139,8 +150,19 @@
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
<p>Our project uses <a href="http://www.atlassian.com/software/jira">JIRA</a>, a Java EE based issue tracking and project management application.</p>
-<h1 id="general-guidance">General guidance</h1>
+<h1 id="general-guidance">General guidance<a class="headerlink" href="#general-guidance" title="Permanent link">¶</a></h1>
<p>First, this is the best place to submit bugs (or what you think is a bug). The mailing list is a short term memory place, don't expect your problem to be answered if it's not in the next couple of days you posted on it.</p>
<p>What are the important informations you need to put when feeling a JIRA ?</p>
<ul>
@@ -152,9 +174,9 @@
<li>Last, not least, if you are kind enough to propose a patch, attach it and <strong>do not forget to check the box which grant The ASF the right to apply it in the code base.</strong></li>
</ul>
<p>Remember that this issue tracking system is public. Would you provide some confidential information, it will be visbile to the world. Keep that in mind before posting !!!</p>
-<h1 id="filling-an-issue">Filling an issue</h1>
+<h1 id="filling-an-issue">Filling an issue<a class="headerlink" href="#filling-an-issue" title="Permanent link">¶</a></h1>
<p>Issues, bugs, and feature requests should be submitted to the following issue tracking system :</p>
-<table>
+<table class="table">
<thead>
<tr>
<th></th>