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 [5/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/mina-project/mailing-lists.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/mailing-lists.html (original)
+++ websites/staging/mina/trunk/content/mina-project/mailing-lists.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>
<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>
@@ -153,30 +175,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/news.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/news.html (original)
+++ websites/staging/mina/trunk/content/mina-project/news.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 @@
-<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>
+<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="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>
@@ -151,13 +173,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>
@@ -215,7 +237,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>
@@ -242,7 +264,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>
@@ -256,33 +278,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>
Modified: websites/staging/mina/trunk/content/mina-project/performances.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/performances.html (original)
+++ websites/staging/mina/trunk/content/mina-project/performances.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,13 +150,24 @@
-<h1 id="before-you-read-the-performance-test-reports">Before You Read the Performance Test Reports...</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="before-you-read-the-performance-test-reports">Before You Read the Performance Test Reports...<a class="headerlink" href="#before-you-read-the-performance-test-reports" title="Permanent link">¶</a></h1>
<p>This page exhibits the performance test results under various conditions (e.g. various protocols and system environments). Please [contact us|Mailing Lists] if you have any specific performance test results to publish for your MINA-based application.</p>
<DIV class="note" markdown="1">
The following performance test results may have critical flaws in test design or contain wrong values. Please regard these reports as just a hint for understanding general performance characteristics of Apache MINA. Additionally, these reports are not meant to claim that Apache MINA outperforms a certain product purposely{note}
</DIV>
-<h2 id="apache-mina-200-m1-snapshot-asyncweb-090-snapshot">Apache MINA 2.0.0-M1-SNAPSHOT + AsyncWeb 0.9.0-SNAPSHOT</h2>
+<h2 id="apache-mina-200-m1-snapshot-asyncweb-090-snapshot">Apache MINA 2.0.0-M1-SNAPSHOT + AsyncWeb 0.9.0-SNAPSHOT<a class="headerlink" href="#apache-mina-200-m1-snapshot-asyncweb-090-snapshot" title="Permanent link">¶</a></h2>
<p><a href="http://gleamynode.net/">Trustin Lee</a> ran a HTTP performance test with the latest snapshot of Apache MINA and <a href="https://svn.apache.org/repos/asf/mina/asyncweb/trunk/">AsyncWeb</a> combo, using <a href="https://svn.apache.org/repos/asf/mina/asyncweb/trunk/examples/src/main/java/org/apache/asyncweb/examples/lightweight/">the AsyncWeb lightweight HTTP server example</a>. </p>
<ul>
<li>Protocol<ul>
Modified: websites/staging/mina/trunk/content/mina-project/quick-start-guide.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/quick-start-guide.html (original)
+++ websites/staging/mina/trunk/content/mina-project/quick-start-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="quick-start-guide">Quick Start Guide</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="quick-start-guide">Quick Start Guide<a class="headerlink" href="#quick-start-guide" title="Permanent link">¶</a></h1>
<p>This tutorial will walk you through the process of building a MINA based program. This tutorial will walk through building a time server. The following prerequisites are required for this tutorial:</p>
<ul>
<li>MINA 2.0.7 Core</li>
@@ -154,7 +176,7 @@
</li>
</ul>
<p>I have tested this program on both Windows© 2000 professional and linux. If you have any problems getting this program to work, please do not hesitate to [contact us|Contact] in order to talk to the MINA developers. Also, this tutorial has tried to remain independent of development environments (IDE, editors..etc). This tutorial will work with any environment that you are comfortable with. Compilation commands and steps to execute the program have been removed for brevity. If you need help learning how to either compile of execute java programs, please consult the <a href="http://java.sun.com/docs/books/tutorial/">Java tutorial</a>.</p>
-<h2 id="writing-the-mina-time-server">Writing the MINA time server</h2>
+<h2 id="writing-the-mina-time-server">Writing the MINA time server<a class="headerlink" href="#writing-the-mina-time-server" title="Permanent link">¶</a></h2>
<p>We will begin by creating a file called MinaTimeServer.java. The initial code can be found below:
:::Java
public class MinaTimeServer {</p>
@@ -331,9 +353,9 @@
</pre></div>
-<h2 id="try-out-the-time-server">Try out the Time server</h2>
+<h2 id="try-out-the-time-server">Try out the Time server<a class="headerlink" href="#try-out-the-time-server" title="Permanent link">¶</a></h2>
<p>At this point, we can go ahead and compile the program. Once you have compiled the program you can run the program in order to test out what happens. The easiest way to test the program is to start the program, and then telnet in to the program:</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Client Output</th>
@@ -347,7 +369,7 @@
</tr>
</tbody>
</table>
-<h2 id="whats-next">What's Next?</h2>
+<h2 id="whats-next">What's Next?<a class="headerlink" href="#whats-next" title="Permanent link">¶</a></h2>
<p>Please visit our <a href="userguide/user-guide-toc.html">User Guide</a> page to find out more resources.</p>
Modified: websites/staging/mina/trunk/content/mina-project/related-projects.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/related-projects.html (original)
+++ websites/staging/mina/trunk/content/mina-project/related-projects.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>Related Projects</H1>
<p>This page lists the projects which use Apache MINA as its networking layer. Please contact us if you are using MINA and you want to add a link to this page. You could also read the users' testimonials. To compare MINA to other network application frameworks, please refer to the 'Other network application frameworks' section below.</p>
@@ -176,54 +198,54 @@
<li><a href="#apache-directory-project">Apache Directory Project</a></li>
<li><a href="#beep4j">Beep4j</a></li>
<li><a href="#vfs-ftpserver-bridge">VFS FTPServer Bridge</a></li>
-<li><a href="#wzxhzdk2hdfs-over-ftp"><a name="HDFSoverFTP" />HDFS over FTP</a></li>
+<li><a href="#hdfs-over-ftp"><a name="HDFSoverFTP" />HDFS over FTP</a></li>
</ul>
</li>
</ul>
</div>
-<h2 id="other-network-application-frameworks">Other network application frameworks</h2>
+<h2 id="other-network-application-frameworks">Other network application frameworks<a class="headerlink" href="#other-network-application-frameworks" title="Permanent link">¶</a></h2>
<DIV class="note" markdown="1">
The projects referred in this section 'Other network application frameworks' are <B>not</B> based on MINA but are their own network application frameworks. These links are provided for users who want to compare MINA to other network application frameworks.
</DIV>
-<h3 id="grizzly"><a href="https://grizzly.java.net/">Grizzly</a></h3>
+<h3 id="grizzly"><a href="https://grizzly.java.net/">Grizzly</a><a class="headerlink" href="#grizzly" title="Permanent link">¶</a></h3>
<p>Grizzly framework has been designed to help developers to take advantage of the Java⢠NIO API. Originally developed under the GlassFish umbrella, the framework is now available as a standalone project. Grizzly goals is to help developers to build scalable and robust servers using NIO.</p>
-<h3 id="netty-3"><a href="http://www.jboss.org/netty/">Netty 3</a></h3>
+<h3 id="netty-3"><a href="http://www.jboss.org/netty/">Netty 3</a><a class="headerlink" href="#netty-3" title="Permanent link">¶</a></h3>
<p>The new version of Netty Trustin Lee is working on now. The Netty project is an effort to provide an asynchronous event-driven network application framework and tools for rapid development of maintainable high performance and high scalability protocol servers and clients.</p>
-<h3 id="nio-framework"><a href="http://nioframework.sourceforge.net/">NIO Framework</a></h3>
+<h3 id="nio-framework"><a href="http://nioframework.sourceforge.net/">NIO Framework</a><a class="headerlink" href="#nio-framework" title="Permanent link">¶</a></h3>
<p>The NIO Framework is a library on top of NIO that hides most of the complexity of plain NIO. With the NIO Framework you can implement high-performance Java network applications without having to deal with all the nasty details of NIO. The issues above are resolved while the performance is preserved.</p>
-<h3 id="quickserver"><a href="http://www.quickserver.org/">QuickServer</a></h3>
+<h3 id="quickserver"><a href="http://www.quickserver.org/">QuickServer</a><a class="headerlink" href="#quickserver" title="Permanent link">¶</a></h3>
<p>QuickServer is an open source Java library/framework for quick creation of robust multi-client TCP server applications. QuickServer provides an abstraction over the ServerSocket, Socket and other network and input output classes and it eases the creation of powerful network servers.</p>
-<h3 id="xsocket"><a href="http://xsocket.sourceforge.net/">xSocket</a></h3>
+<h3 id="xsocket"><a href="http://xsocket.sourceforge.net/">xSocket</a><a class="headerlink" href="#xsocket" title="Permanent link">¶</a></h3>
<p>xSocket is a easy to use NIO-based library to build high performance, highly scalable network applications. It supports writing client-side applications as well as server-side applications in an intuitive way. Issues like low level NIO selector programming, connection pool management, connection timeout detection or fragmented buffer reads are encapsulated by xSocket.</p>
-<h2 id="messaging">Messaging</h2>
-<h3 id="apache-camel"><a href="http://activemq.apache.org/camel/">Apache Camel</a></h3>
+<h2 id="messaging">Messaging<a class="headerlink" href="#messaging" title="Permanent link">¶</a></h2>
+<h3 id="apache-camel"><a href="http://activemq.apache.org/camel/">Apache Camel</a><a class="headerlink" href="#apache-camel" title="Permanent link">¶</a></h3>
<p>Apache Camel is a POJO routing and mediation library for working with files, FTP, HTTP, MINA, JMS, JBI and web services.</p>
-<h3 id="apache-qpid-incubating"><a href="http://cwiki.apache.org/qpid/">Apache Qpid (incubating)</a></h3>
+<h3 id="apache-qpid-incubating"><a href="http://cwiki.apache.org/qpid/">Apache Qpid (incubating)</a><a class="headerlink" href="#apache-qpid-incubating" title="Permanent link">¶</a></h3>
<p>The Apache Qpid Project implemented <a href="http://www.amqp.org/">AMQP (Advanced Message Queuing Protocol)</a> using Apache MINA.</p>
-<h3 id="avis"><a href="http://avis.sourceforge.net/">Avis</a></h3>
+<h3 id="avis"><a href="http://avis.sourceforge.net/">Avis</a><a class="headerlink" href="#avis" title="Permanent link">¶</a></h3>
<p>Avis is an event router service compatible with the commercial Elvin implementation developed by Mantara Software. Avis provides a fast, general-purpose publish/subscribe message bus.</p>
-<h3 id="mailstersmtp"><a href="http://tedorg.free.fr/en/projects.php?section=smtp">MailsterSMTP</a></h3>
+<h3 id="mailstersmtp"><a href="http://tedorg.free.fr/en/projects.php?section=smtp">MailsterSMTP</a><a class="headerlink" href="#mailstersmtp" title="Permanent link">¶</a></h3>
<p>MailsterSMTP is designed to be a easy to understand Java library which provides a receptive SMTP server component. Using this library, you can easily receive mails using a simple Java interface, extend the set of implemented commands or control how mails are delivered by plugging your custom implementations.</p>
-<h2 id="instant-messaging">Instant Messaging</h2>
-<h3 id="jive-software-openfire"><a href="http://www.jivesoftware.com/products/openfire/">Jive Software Openfire</a></h3>
+<h2 id="instant-messaging">Instant Messaging<a class="headerlink" href="#instant-messaging" title="Permanent link">¶</a></h2>
+<h3 id="jive-software-openfire"><a href="http://www.jivesoftware.com/products/openfire/">Jive Software Openfire</a><a class="headerlink" href="#jive-software-openfire" title="Permanent link">¶</a></h3>
<p>Jive Software Openfire implemented <a href="http://www.xmpp.org/">XMPP (Extensible Messaging and Presence Protocol)</a> server on top of Apache MINA. After switching to Apache MINA, <a href="http://community.igniterealtime.org/blogs/ignite/2006/12/19/scalability-turn-it-to-eleven/">they gained 11 times scalability boost</a>.</p>
-<h2 id="media-storage-streaming">Media Storage & Streaming</h2>
-<h3 id="openlsd"><a href="http://openlsd.free.fr/en/OpenLSD.html">OpenLSD</a></h3>
+<h2 id="media-storage-streaming">Media Storage & Streaming<a class="headerlink" href="#media-storage-streaming" title="Permanent link">¶</a></h2>
+<h3 id="openlsd"><a href="http://openlsd.free.fr/en/OpenLSD.html">OpenLSD</a><a class="headerlink" href="#openlsd" title="Permanent link">¶</a></h3>
<p>OpenLSD is an open source framework for massive document archiving. The web site also contains an interesting performance test report.</p>
-<h3 id="red5"><a href="http://www.osflash.org/red5">Red5</a></h3>
+<h3 id="red5"><a href="http://www.osflash.org/red5">Red5</a><a class="headerlink" href="#red5" title="Permanent link">¶</a></h3>
<p>OSFlash.org team implemented an open-source flash media streaming (<a href="http://en.wikipedia.org/wiki/Real_Time_Messaging_Protocol">RTMP, Real Time Messaging Protocol</a>) server with Apache MINA.</p>
-<h2 id="finance">Finance</h2>
-<h3 id="quickfixj"><a href="http://www.quickfixj.org/">QuickFIX/J</a></h3>
+<h2 id="finance">Finance<a class="headerlink" href="#finance" title="Permanent link">¶</a></h2>
+<h3 id="quickfixj"><a href="http://www.quickfixj.org/">QuickFIX/J</a><a class="headerlink" href="#quickfixj" title="Permanent link">¶</a></h3>
<p>QuickFIX/J is a Java implementation of <a href="http://www.fixprotocol.org/">FIX (Financial Information eXchange) protocol</a>.</p>
-<h2 id="miscellaneous">Miscellaneous</h2>
-<h3 id="apache-directory-project"><a href="http://directory.apache.org/">Apache Directory Project</a></h3>
+<h2 id="miscellaneous">Miscellaneous<a class="headerlink" href="#miscellaneous" title="Permanent link">¶</a></h2>
+<h3 id="apache-directory-project"><a href="http://directory.apache.org/">Apache Directory Project</a><a class="headerlink" href="#apache-directory-project" title="Permanent link">¶</a></h3>
<p>The Apache Directory Project implemented LDAP v3, Kerberos, DNS, DHCP, NTP, and ChangePW using Apache MINA.</p>
-<h3 id="beep4j"><a href="http://beep4j.sourceforge.net/">Beep4j</a></h3>
+<h3 id="beep4j"><a href="http://beep4j.sourceforge.net/">Beep4j</a><a class="headerlink" href="#beep4j" title="Permanent link">¶</a></h3>
<p>Beep4j is an open-source implementation of the <a href="http://www.beepcore.org/">BEEP</a> specification (RFC3080 and RFC3081).</p>
-<h3 id="vfs-ftpserver-bridge"><a href="http://vfs-utils.sourceforge.net/ftpserver/index.html">VFS FTPServer Bridge</a></h3>
+<h3 id="vfs-ftpserver-bridge"><a href="http://vfs-utils.sourceforge.net/ftpserver/index.html">VFS FTPServer Bridge</a><a class="headerlink" href="#vfs-ftpserver-bridge" title="Permanent link">¶</a></h3>
<p>This project provides an Apache Commons VFS implementation for the Apache FTPServer project. Instead of working only on local files, with this VFS bridge you can connect to any VFS provider. You can still use a local file system, but you can also use a ZIP file, loop through to another FTP server, or use any other available VFS implementation such as DctmVFS.</p>
-<h3 id="wzxhzdk2hdfs-over-ftp"><a name="HDFSoverFTP" /><a href="https://sites.google.com/a/iponweb.net/hadoop/Home/hdfs-over-ftp">HDFS over FTP</a></h3>
+<h3 id="hdfs-over-ftp"><a name="HDFSoverFTP" /><a href="https://sites.google.com/a/iponweb.net/hadoop/Home/hdfs-over-ftp">HDFS over FTP</a><a class="headerlink" href="#hdfs-over-ftp" title="Permanent link">¶</a></h3>
<p>FTP server which works on a top of HDFS. It aAllows to connect to HDFS using any FTP client. FTP server is configurable by hdfs-over-ftp.conf and users.conf. Also it allows to use secure connection over SSL and supports all HDFS permissions</p>
Modified: websites/staging/mina/trunk/content/mina-project/road-map.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/road-map.html (original)
+++ websites/staging/mina/trunk/content/mina-project/road-map.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,12 +150,23 @@
+<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>Please click the following links to find out what issues have been resolved and what issues will be resolved.</p>
<ul>
<li><a href="http://issues.apache.org/jira/browse/DIRMINA?report=com.atlassian.jira.plugin.system.project:roadmap-panel&subset=-1">Road map for the future releases</a></li>
<li><a href="http://issues.apache.org/jira/browse/DIRMINA?report=com.atlassian.jira.plugin.system.project:changelog-panel&subset=-1">Change log for the past releases</a></li>
</ul>
-<h2 id="genesis-of-mina">Genesis of MINA</h2>
+<h2 id="genesis-of-mina">Genesis of MINA<a class="headerlink" href="#genesis-of-mina" title="Permanent link">¶</a></h2>
<p>by Trustin Lee </p>
<p>In June 2004, I released a network application framework, 'Netty2'. It was the first network application framework that provides event-based architecture in Java community. It attracted network application programmers because of its simplicity and ease of use. As the Netty2 community matured, its problems also arose. Netty2 didn't work fine with text protocols and had a critical architectural flaw that prevents users from using it for applications with many concurrent clients.</p>
<p>Quite a large amount of information was collected about what users like about Netty2 and what improvements they want from it for 6 months. It was clear they like its ease of use and unit-testability. They wanted support for UDP/IP and text protocols. I had to invent a cleaner, more flexible, and more extensible API so that it is easy to learn yet full-featured.</p>
Modified: websites/staging/mina/trunk/content/mina-project/set-svnprops-tortoisesvn.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/set-svnprops-tortoisesvn.html (original)
+++ websites/staging/mina/trunk/content/mina-project/set-svnprops-tortoisesvn.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="setting-svn-properties-in-tortoise-svn">Setting SVN Properties in Tortoise SVN</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="setting-svn-properties-in-tortoise-svn">Setting SVN Properties in Tortoise SVN<a class="headerlink" href="#setting-svn-properties-in-tortoise-svn" title="Permanent link">¶</a></h1>
<p>This article is for configuring SVN properties for TortoiseSVN Client</p>
<p>To maintain header's with revision tags like, we need to set SVN properties.</p>
<div class="codehilite"><pre><span class="cm">/**</span>
Modified: websites/staging/mina/trunk/content/mina-project/sources.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/sources.html (original)
+++ websites/staging/mina/trunk/content/mina-project/sources.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,25 +150,36 @@
-<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>
+<h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">¶</a></h2>
<p>Sources for the Apache MINA projects are currently managed through GIT. Instructions on GIT use can be found at <a href="http://git-scm.com/book/">http://git-scm.com/book/</a>.</p>
<p>For each project you can find a detailed description how to checkout and build the source on the project documentation. This page is just a short overview.</p>
-<h1 id="normal-git-access">Normal Git Access</h1>
+<h1 id="normal-git-access">Normal Git Access<a class="headerlink" href="#normal-git-access" title="Permanent link">¶</a></h1>
<p>Anyone can check code out of Git. You only need to specify a username and password in order to update the Git repository, and only MINA committers have the permissions to do that. We run Git over standard HTTPS, so hopefully you won't have problems with intervening firewalls.</p>
-<h2 id="web-access">Web Access</h2>
+<h2 id="web-access">Web Access<a class="headerlink" href="#web-access" title="Permanent link">¶</a></h2>
<p>The following is a link to the <a href="https://git-wip-us.apache.org/repos/asf?p=mina.git;a=summary">online source repository</a>.</p>
-<h1 id="cloning-from-the-git-repo">Cloning from the Git repo</h1>
+<h1 id="cloning-from-the-git-repo">Cloning from the Git repo<a class="headerlink" href="#cloning-from-the-git-repo" title="Permanent link">¶</a></h1>
<p>Again, anyone can do this. Use a command like to checkout the current development version (the trunk):</p>
-<h3 id="for-mina">For MINA</h3>
+<h3 id="for-mina">For MINA<a class="headerlink" href="#for-mina" title="Permanent link">¶</a></h3>
<p>read only access :</p>
<p>git clone http://git-wip-us.apache.org/repos/asf/mina.git mina</p>
<p>write access :</p>
<p>git clone https://git-wip-us.apache.org/repos/asf/mina.git mina</p>
-<h1 id="building-mina">Building MINA</h1>
+<h1 id="building-mina">Building MINA<a class="headerlink" href="#building-mina" title="Permanent link">¶</a></h1>
<p>Instructions on how to build MINA can be found <a href="developer-guide.html">here</a></p>
-<h1 id="released-version">Released version</h1>
+<h1 id="released-version">Released version<a class="headerlink" href="#released-version" title="Permanent link">¶</a></h1>
<p>The following table displays the URL of each project, and the URL where you can find information about how to build each project.</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Subproject/Documentation</th>
@@ -187,9 +209,9 @@
</tr>
</tbody>
</table>
-<h1 id="commit-changes-to-git">Commit Changes to Git</h1>
+<h1 id="commit-changes-to-git">Commit Changes to Git<a class="headerlink" href="#commit-changes-to-git" title="Permanent link">¶</a></h1>
<p>In order to be able to push some modification, you have to be a committer.</p>
-<h1 id="documentation">Documentation</h1>
+<h1 id="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h1>
<p>The Website documentation is published via Apache SVN pubsub. The website source resides at</p>
<p><a href="https://svn.apache.org/repos/asf/mina/site/trunk">https://svn.apache.org/repos/asf/mina/site/trunk</a></p>
Modified: websites/staging/mina/trunk/content/mina-project/testimonials.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/testimonials.html (original)
+++ websites/staging/mina/trunk/content/mina-project/testimonials.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>
<p><a href="http://practicingtechie.wordpress.com/2012/08/06/asynchronous-event-driven-servers-with-apache-mina/"><strong>Marko Asplund</strong></a> says:</p>
<blockquote>
<p>I found that Apache MINA really did fulfill its promise and implementing a high-performance, scalable and extensible network server was easy using it. MINA also helps very cleanly separate network communication and application level message processing logic. Supporting multiple different protocols in in the same server is well supported in MINA. As a downside the documentation for v2.0 is a bit lacking, but fortunately there are quite a few code samples that you can check out.</p>
Modified: websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/ch1-getting-started.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/ch1-getting-started.html (original)
+++ websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/ch1-getting-started.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>
@@ -158,7 +169,18 @@
</div>
-<h1 id="chapter-1-getting-started">Chapter 1 - Getting Started</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="chapter-1-getting-started">Chapter 1 - Getting Started<a class="headerlink" href="#chapter-1-getting-started" title="Permanent link">¶</a></h1>
<p>In this chapter, we will give you first sense of what is <strong>MINA</strong>, what is <strong>NIO</strong>, why we developped a framework on top of <strong>NIO</strong> and what you will find inside.
We will also show you how to run a very simple example of a server run with <strong>MINA</strong></p>
<ol>
Modified: websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/features.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/features.html (original)
+++ websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/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>
@@ -158,7 +169,18 @@
</div>
-<h1 id="features">Features</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="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/userguide/ch1-getting-started/first-steps.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/first-steps.html (original)
+++ websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/first-steps.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>
@@ -158,13 +169,24 @@
</div>
-<h1 id="first-steps">First Steps</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="first-steps">First Steps<a class="headerlink" href="#first-steps" title="Permanent link">¶</a></h1>
<p>We will show you how easy it is to use MINA, running a very simple example provided with the <strong>MINA</strong> package. </p>
<p>The first thing you have to do is to setup your evnvironment when you want to use <strong>MINA</strong> in your application. We will describe what you need to install and how to run a <strong>MINA</strong> program. Nothing fancy, just a first taste of <strong>MINA</strong>...</p>
-<h2 id="download">Download</h2>
+<h2 id="download">Download<a class="headerlink" href="#download" title="Permanent link">¶</a></h2>
<p>First, you have to download the latest <strong>MINA</strong> release from <a href="../../downloads.html">Downloads Section</a>. Just take the latest version, unless you have very good reasons not to do so...</p>
<p>Generally speaking, if you are going to use <strong>Maven</strong> to build your project, you won't even have to download anything, as soon as you will depend on a repository which already contains the <strong>MINA</strong> libraries : you just tell your <strong>Maven</strong> poms that you want to use the <strong>MINA</strong> jars you need.</p>
-<h2 id="whats-inside">What's inside</h2>
+<h2 id="whats-inside">What's inside<a class="headerlink" href="#whats-inside" title="Permanent link">¶</a></h2>
<p>After the download is complete, extract the content of <em>tar.gz</em> or <em>zip</em> file to local hard drive. The downloaded compressed file has following contents</p>
<p>On UNIX system, type :</p>
<div class="codehilite"><pre>$ <span class="n">tar</span> <span class="n">xzpf</span> <span class="n">apache</span><span class="o">-</span><span class="n">mina</span><span class="o">-</span>2<span class="p">.</span>0<span class="p">.</span>7<span class="o">-</span><span class="n">tar</span><span class="p">.</span><span class="n">gz</span>
@@ -186,14 +208,14 @@
</pre></div>
-<h2 id="content-details">Content Details</h2>
+<h2 id="content-details">Content Details<a class="headerlink" href="#content-details" title="Permanent link">¶</a></h2>
<ul>
<li><em>dist</em> - Contains jars for the <strong>MINA</strong> library code</li>
<li><em>docs</em> - Contains API docs and Code xrefs</li>
<li><em>lib</em> - Contains all needed jars for all the libraries needed for using <strong>MINA</strong></li>
</ul>
<p>Additional to these, the base directory has couple of license and notice files</p>
-<h1 id="running-your-first-mina-program">Running your first MINA program</h1>
+<h1 id="running-your-first-mina-program">Running your first MINA program<a class="headerlink" href="#running-your-first-mina-program" title="Permanent link">¶</a></h1>
<p>Well, we have downloaded the release, let's run our first <strong>MINA</strong> example, shipped with the release.</p>
<p>Put the following jars in the classpath</p>
<ul>
Modified: websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/nio-overview.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/nio-overview.html (original)
+++ websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/nio-overview.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>
@@ -158,7 +169,18 @@
</div>
-<h1 id="nio-overview">NIO 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="nio-overview">NIO Overview<a class="headerlink" href="#nio-overview" title="Permanent link">¶</a></h1>
<p>The <strong>NIO</strong> API was introduced in <strong>Java 1.4</strong> and had since been used for wide number of applications. The <strong>NIO</strong> API covers <strong>IO</strong> non-blocking operations.</p>
<DIV class="note" markdown="1">
First of all, it's good to know that <strong>MINA</strong> is written on top of <strong>NIO 1</strong>. A new version has been designed in <strong>Java 7</strong>, <strong>NIO-2</strong>, we don't yet benefit from the added features this version is carrying.
@@ -178,7 +200,7 @@
</ul>
<p>We are mostly interested in the <em>Channels</em>, _ Selectors_ and <em>Buffers</em> parts in the <strong>MINA</strong> framework, except that we want to hide those elements to the user. </p>
<p>This user guide will thus focus on everything built on top of those internal components.</p>
-<h1 id="nio-vs-bio">NIO vs BIO</h1>
+<h1 id="nio-vs-bio">NIO vs BIO<a class="headerlink" href="#nio-vs-bio" title="Permanent link">¶</a></h1>
<p>It's important to understand the difference between those two APIs. <strong>BIO</strong>, or <strong>Blocking</strong> <strong>IO</strong>, relies on plain sockets used in a blocking mode : when you read, write or do whatever operation on a socket, the called operation will blcok the caller until the operation is completed.</p>
<p>In some cases, it's critical to be able to call the operation, and to expect the called operation to inform the caller when the operation is done : the caller can then do something else in the mean time.</p>
<p>This is also where <strong>NIO</strong> offers a better way to handle <strong>IO</strong> when you have numerous connected sockets : you dn't have to create a specific thread for each connection, you can just use a few threads to do the same job.</p>
Modified: websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/summary.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/summary.html (original)
+++ websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/summary.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>
@@ -158,7 +169,18 @@
</div>
-<h1 id="summary">Summary</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="summary">Summary<a class="headerlink" href="#summary" title="Permanent link">¶</a></h1>
<p>In this chapter, we looked at MINA based Application Architecture, for Client as well as Server. We also touched upon the implementation of Sample TCP Server/Client, and UDP Server and Client.</p>
<p>In the chapters to come we shall discuss about MINA Core constructs and advanced topics</p>
Modified: websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/why-mina.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/why-mina.html (original)
+++ websites/staging/mina/trunk/content/mina-project/userguide/ch1-getting-started/why-mina.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>
@@ -158,16 +169,27 @@
</div>
-<h1 id="why-mina">Why 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="why-mina">Why MINA ?<a class="headerlink" href="#why-mina" title="Permanent link">¶</a></h1>
<p>Writing some network application is generrally seen as a burden, and a low level development. It's a area which is not frequently studied or known by developpers, either because it has ben studied in school a long time ago and everything has been forgotten, or because the complexity of this network layer is frequently hidden by higher level layers, so you never get deep into it.</p>
<p>Add that when it comes to asynchronous IO, an extra layer of complexity comes into play : time.</p>
<p>The big difference between <strong>BIO</strong> (Blocking IO) and <strong>NIO</strong> (Non-Blocking IO) is that in <strong>BIO</strong>, you send a request, and you wait until you get the response. On the server side, it means one thread wil be associated with any incoming connection, so you won't have to deal with the complexity of multiplexing the connections. In <strong>NIO</strong>, on the other hand, you have to deal with the synchronous nature of a non-blocking system, wich means that your application will be invoked when some events occur. In <strong>NIO</strong>, you don't call and wait for a result, you send a command and you are informed when the result is ready.</p>
-<h2 id="the-need-of-a-framework">The need of a framework</h2>
+<h2 id="the-need-of-a-framework">The need of a framework<a class="headerlink" href="#the-need-of-a-framework" title="Permanent link">¶</a></h2>
<p>Considering those differences, and teh fact that most of the applications are usually expecting a blocking mode when invoking the network layer, the best solution is to hide this aspect by writing a framework that mimic a blocking mode. This is what <strong>MINA</strong> does !</p>
<p>But <strong>MINA</strong> does more. It provides a common IO vision to an application that needs to communicate over <strong>TCP</strong>, <strong>UDP</strong> or whatever mechanism. If we consider only <strong>TCP</strong> and <strong>UDP</strong>, one is a connected protocol (<strong>TCP</strong>) when the other one is connectionless (<strong>UDP</strong>). <strong>MINA</strong> masks this difference, and make you focus on the two parts that are important for your application : the applicive code and the application protocol encoding/decoding.</p>
<p><strong>MINA</strong> does not only handles <strong>TCP</strong> and <strong>UDP</strong>, it's also offering a layer on top of serial communication (<strong>RSC232</strong>), over <strong>VmpPipe</strong> or <strong>APR</strong>. </p>
<p>Last, not least, <strong>MINA</strong> is a network framework that has been specifically designed to work either on the client side and on teh server side. Writing a server make it critical to have a scalable system, which is tunnable to fit the server needs, in term of performance and memory usage : this is what <strong>MINA</strong> is good for, still making it easy to devlop you server.</p>
-<h2 id="when-to-use-mina">When to use MINA ?</h2>
+<h2 id="when-to-use-mina">When to use MINA ?<a class="headerlink" href="#when-to-use-mina" title="Permanent link">¶</a></h2>
<p>This is a intersting question ! <strong>MINA</strong> does not expect to be the best possible choice in any case. There are a few elements to consider when considering using <strong>MINA</strong>. Let's list them :</p>
<ul>
<li>
Modified: websites/staging/mina/trunk/content/mina-project/userguide/ch10-executor-filter/ch10-executor-filter.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/userguide/ch10-executor-filter/ch10-executor-filter.html (original)
+++ websites/staging/mina/trunk/content/mina-project/userguide/ch10-executor-filter/ch10-executor-filter.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>
@@ -158,13 +169,24 @@
</div>
+<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="chapter-10-executor-filter">Chapter 10 - Executor Filter</h1>
+<h1 id="chapter-10-executor-filter">Chapter 10 - Executor Filter<a class="headerlink" href="#chapter-10-executor-filter" title="Permanent link">¶</a></h1>
<p>MINA 1.X version let the user define the Thread Model at the Acceptor level. It was part of the Acceptor configuration. This led to complexity, and the MINA team decided to remove this option, replacing it with a much more versatile system, based on a filter : the <strong>ExecutorFilter</strong>.</p>
-<h2 id="the-executorfilter-class">The ExecutorFilter class</h2>
+<h2 id="the-executorfilter-class">The ExecutorFilter class<a class="headerlink" href="#the-executorfilter-class" title="Permanent link">¶</a></h2>
<p>This class is implementing the IoFilter interface, and basically, it contains an Executor to spread the incoming events to a pool of threads. This will allow an application to use more efficiently the processors, if some task is CPU intensive.</p>
<p>This Filter can be used just before the handlers, assuming that most of the processing will be done in your application, or somewhere before some CPU intensive filter (for instance, a CodecFilter).</p>
<p>More to come ...</p>
Modified: websites/staging/mina/trunk/content/mina-project/userguide/ch11-ssl-filter/ch11-ssl-filter.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/userguide/ch11-ssl-filter/ch11-ssl-filter.html (original)
+++ websites/staging/mina/trunk/content/mina-project/userguide/ch11-ssl-filter/ch11-ssl-filter.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>
@@ -158,7 +169,18 @@
</div>
-<h1 id="chapter-11-ssl-filter">Chapter 11 - SSL Filter</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="chapter-11-ssl-filter">Chapter 11 - SSL Filter<a class="headerlink" href="#chapter-11-ssl-filter" title="Permanent link">¶</a></h1>
<p>To be completed...</p>
Modified: websites/staging/mina/trunk/content/mina-project/userguide/ch12-logging-filter/ch12-logging-filter.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/userguide/ch12-logging-filter/ch12-logging-filter.html (original)
+++ websites/staging/mina/trunk/content/mina-project/userguide/ch12-logging-filter/ch12-logging-filter.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>
@@ -158,7 +169,18 @@
</div>
-<h1 id="chapter-12-logging-filter">Chapter 12 - Logging Filter</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="chapter-12-logging-filter">Chapter 12 - Logging Filter<a class="headerlink" href="#chapter-12-logging-filter" title="Permanent link">¶</a></h1>
<div class="toc">
<ul>
<li><a href="#chapter-12-logging-filter">Chapter 12 - Logging Filter</a></li>
@@ -173,13 +195,13 @@
</li>
</ul>
</div>
-<h1 id="background">Background</h1>
+<h1 id="background">Background<a class="headerlink" href="#background" title="Permanent link">¶</a></h1>
<p>The Apache MINA uses a system that allows for the developer of the MINA-base application to use their own logging system.</p>
-<h2 id="slf4j">SLF4J</h2>
+<h2 id="slf4j">SLF4J<a class="headerlink" href="#slf4j" title="Permanent link">¶</a></h2>
<p>MINA employs the Simple Logging Facade for Java (SLF4J). You can find information on SLF4J here. This logging utility allows for the implementation of any number of logging systems. You may use log4j, java.util.logging or other logging systems. The nice part about this is that if you want to change from java.util.logging to log4j later on in the development process, you do not need to change your source code at all.</p>
-<h3 id="choosing-the-right-jars">Choosing the Right JARs</h3>
+<h3 id="choosing-the-right-jars">Choosing the Right JARs<a class="headerlink" href="#choosing-the-right-jars" title="Permanent link">¶</a></h3>
<p>SLF4J uses a static binding. This means there is one JAR file for each supported logging framework. You can use your favorite logging framework by choosing the JAR file that calls the logging framework you chose statically. The following is the table of required JAR files to use a certain logging framework.</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Logging framework</th>
@@ -212,9 +234,9 @@
<li>The version of slf4j-api.jar and slf4j-<impl>.jar should be identical.</li>
</ul>
<p>Once configured properly, you can continue to configure the actual logging framework you chose (e.g. modifying log4j.properties).</p>
-<h3 id="overriding-jakarta-commons-logging">Overriding Jakarta Commons Logging</h3>
+<h3 id="overriding-jakarta-commons-logging">Overriding Jakarta Commons Logging<a class="headerlink" href="#overriding-jakarta-commons-logging" title="Permanent link">¶</a></h3>
<p>SLF4J also provides a way to convert the existing applications that use Jakarta Commons Logging to use SLF4J without changing the application code. Just remove commons-loggong JAR file from the class path, and add jcl104-over-slf4j.jar to the class path.</p>
-<h2 id="log4j-example">log4j example</h2>
+<h2 id="log4j-example">log4j example<a class="headerlink" href="#log4j-example" title="Permanent link">¶</a></h2>
<p>For this example we will use the log4j logging system. We set up a project and place the following snippet into a file called log4j.properties:</p>
<div class="codehilite"><pre><span class="c"># Set root logger level to DEBUG and its only appender to A1.</span>
<span class="n">log4j</span><span class="p">.</span><span class="n">rootLogger</span><span class="p">=</span><span class="n">DEBUG</span><span class="p">,</span> <span class="n">A1</span>
@@ -251,7 +273,7 @@
<p>As you can see we removed the addLogger method and added in the 2 lines added to the example EchoServer. With a reference to the LoggingFilter, you can set the logging level per event type in your handler that is associated with the IoAcceptor here. In order to specify the IoHandler events that trigger logging and to what levels the logging is performed, there is a method in the LoggingFilter called setLogLevel(IoEventType, LogLevel). Below are the options for this method:</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>IoEventType</th>
@@ -290,7 +312,7 @@
</tbody>
</table>
<p>Here are the descriptions of the LogLevels:</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>LogLevel</th>
Modified: websites/staging/mina/trunk/content/mina-project/userguide/ch13-debugging/ch13-debugging.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/userguide/ch13-debugging/ch13-debugging.html (original)
+++ websites/staging/mina/trunk/content/mina-project/userguide/ch13-debugging/ch13-debugging.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>
@@ -158,7 +169,18 @@
</div>
-<h1 id="chapter-13-debugging">Chapter 13 - Debugging</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="chapter-13-debugging">Chapter 13 - Debugging<a class="headerlink" href="#chapter-13-debugging" title="Permanent link">¶</a></h1>
<p>To be completed...</p>