You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mina.apache.org by ap...@apache.org on 2012/09/27 17:51:46 UTC
svn commit: r1391063 - in /mina/site/trunk: content/downloads.mdtext
content/sources.mdtext content/testimonials.mdtext templates/header.html
Author: apaliwal
Date: Thu Sep 27 15:51:46 2012
New Revision: 1391063
URL: http://svn.apache.org/viewvc?rev=1391063&view=rev
Log:
few more pages moved
Added:
mina/site/trunk/content/sources.mdtext
mina/site/trunk/content/testimonials.mdtext
Modified:
mina/site/trunk/content/downloads.mdtext
mina/site/trunk/templates/header.html
Modified: mina/site/trunk/content/downloads.mdtext
URL: http://svn.apache.org/viewvc/mina/site/trunk/content/downloads.mdtext?rev=1391063&r1=1391062&r2=1391063&view=diff
==============================================================================
--- mina/site/trunk/content/downloads.mdtext (original)
+++ mina/site/trunk/content/downloads.mdtext Thu Sep 27 15:51:46 2012
@@ -74,6 +74,10 @@ $ gpg --verify mina-1.2.3.tar.gz.asc
The snapshot JAR files can be found at the [ASF Maven 2 snapshot repository](http://people.apache.org/repo/m2-snapshot-repository/org/apache/mina/). Please note that we don't provide the full distribution (e.g. tarball) of the latest pre-release snapshots. Please check out the source code from our [subversion repository](developer_guide.html) to build the full distribution by yourself.
+# Previous Releases
+
+The previous releases can be found [here](http://archive.apache.org/dist/mina/). Please note that the following releases contains a LGPL licensed file, rxtx-2.1.7.jar: 2.0.0-M4, 2.0.0-M5, 2.0.0-M6, 2.0.0-RC1.
+
# Version Numbering Scheme
The version number of MINA has the following form:
Added: mina/site/trunk/content/sources.mdtext
URL: http://svn.apache.org/viewvc/mina/site/trunk/content/sources.mdtext?rev=1391063&view=auto
==============================================================================
--- mina/site/trunk/content/sources.mdtext (added)
+++ mina/site/trunk/content/sources.mdtext Thu Sep 27 15:51:46 2012
@@ -0,0 +1,137 @@
+Title: Sources
+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
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+ .
+ http://www.apache.org/licenses/LICENSE-2.0
+ .
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+
+Sources for the Apache MINA projects are currently managed through Subversion (SVN). Instructions on Subversion use can be found at <http://svnbook.red-bean.com/>. If you are on Windows, the excellent TortoiseSVN client is highly recommended.
+
+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.
+
+# Web Access to Subversion
+
+If you just want to browse the source code, you can use the [web interface to Subversion](http://svn.apache.org/viewvc/mina). This is current at all times.
+
+# Normal Subversion Access
+
+Anyone can check code out of Subversion. You only need to specify a username and password in order to update the Subversion repository, and only MINA committers have the permissions to do that. We run Subversion over standard HTTPS, so hopefully you won't have problems with intervening firewalls.
+
+# Check out from Subversion
+
+Again, anyone can do this. Use a command like to checkout the current development version (the trunk):
+
+### For MINA
+
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE>svn checkout http://svn.apache.org/repos/asf/mina/trunk
+</PRE>
+</DIV></DIV>
+
+### For FtpServer
+
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE>svn checkout http://svn.apache.org/repos/asf/mina/ftpserver/trunk
+</PRE>
+</DIV></DIV>
+
+### For AsyncWeb
+
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE>svn checkout http://svn.apache.org/repos/asf/mina/asyncweb/trunk
+</PRE>
+</DIV></DIV>
+
+# Building MINA
+
+Instructions on how to build MINA can be found [here](developer_guide.html)
+
+# Released version
+
+The following table displays the URL of each project, and the URL where you can find information about how to build each project.
+
+<DIV class="table-wrap">
+<TABLE class="confluenceTable"><TBODY>
+<TR>
+<TH class="confluenceTh"> Subproject/Documentation </TH>
+<TH class="confluenceTh"> SVN URL </TH>
+</TR>
+<TR>
+<TD class="confluenceTd"> <A href="http://mina.apache.org/developer-guide.html" class="external-link" rel="nofollow">MINA 1.0</A> </TD>
+<TD class="confluenceTd"> <A href="http://svn.apache.org/repos/asf/mina/branches/1.0/" class="external-link" rel="nofollow">http://svn.apache.org/repos/asf/mina/branches/1.0/</A> </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> <A href="http://mina.apache.org/developer-guide.html" class="external-link" rel="nofollow">MINA 1.1</A> </TD>
+<TD class="confluenceTd"> <A href="http://svn.apache.org/repos/asf/mina/branches/1.1/" class="external-link" rel="nofollow">http://svn.apache.org/repos/asf/mina/branches/1.1/</A> </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> <A href="http://mina.apache.org/developer-guide.html" class="external-link" rel="nofollow">MINA 2.0</A> </TD>
+<TD class="confluenceTd"> <A href="http://svn.apache.org/repos/asf/mina/trunk/" class="external-link" rel="nofollow">http://svn.apache.org/repos/asf/mina/trunk/</A> </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> <A href="http://mina.apache.org/developer-guide.html" class="external-link" rel="nofollow">FtpServer 1.0 (dev) </A> </TD>
+<TD class="confluenceTd"> <A href="http://svn.apache.org/repos/asf/mina/ftpserver/trunk/" class="external-link" rel="nofollow">http://svn.apache.org/repos/asf/mina/ftpserver/trunk/</A> </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> <A href="http://mina.apache.org/developer-guide.html" class="external-link" rel="nofollow">AsyncWeb (dev)</A> </TD>
+<TD class="confluenceTd"> <A href="http://svn.apache.org/repos/asf/mina/asyncweb/trunk/" class="external-link" rel="nofollow">http://svn.apache.org/repos/asf/mina/asyncweb/trunk/</A> </TD>
+</TR>
+</TBODY></TABLE>
+</DIV>
+
+# Commit Changes to Subversion
+
+Any __MINA__ committer should have a shell account on svn.apache.org. Before you can commit, you'll need to set a Subversion password for yourself. To do that, log in to svn.apache.org and run the command svnpasswd.
+
+Once your password is set, you can use a command like this to commit:
+
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE>svn commit
+</PRE>
+</DIV></DIV>
+
+If Subversion can't figure out your username, you can tell it explicitly:
+
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE>svn --username you commit
+</PRE>
+</DIV></DIV>
+
+Subversion will prompt you for a password, and once you enter it once, it will remember it for you. Note this is the password you configured with svnpasswd, not your shell or other password.
+
+<DIV class="panelMacro"><TABLE class="noteMacro"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD valign="top"><IMG src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>For committers to be able to commit modification, they should have had checked out the project files using <B>https</B> instead of <B>http</B>.</TD></TR></TABLE></DIV>
+
+## Access from behind a firewall
+
+For those users who are stuck behind a corporate firewall which is blocking http access to the Subversion repository, you can try to access it via the developer connection:
+
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE>$ svn checkout https://svn.apache.org/repos/asf/mina/tags/1.0.10 mina-1.0.10
+</PRE>
+</DIV></DIV>
+
+## Access through a proxy
+
+The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The files location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.)
+
+There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created.
+
+Example : Edit the 'servers' file and add something like :
+
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE>[global]
+http-proxy-host = your.proxy.name
+http-proxy-port = 3128
+</PRE>
+</DIV></DIV>
Added: mina/site/trunk/content/testimonials.mdtext
URL: http://svn.apache.org/viewvc/mina/site/trunk/content/testimonials.mdtext?rev=1391063&view=auto
==============================================================================
--- mina/site/trunk/content/testimonials.mdtext (added)
+++ mina/site/trunk/content/testimonials.mdtext Thu Sep 27 15:51:46 2012
@@ -0,0 +1,119 @@
+Title: Testimonials
+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
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+ .
+ http://www.apache.org/licenses/LICENSE-2.0
+ .
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+
+[__Marko Asplund__](http://practicingtechie.wordpress.com/2012/08/06/asynchronous-event-driven-servers-with-apache-mina/) says:
+
+> 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.
+
+__Maarten Bosteels__ says:
+
+> EURid used MINA during the landrush for .eu domain names on the 7th of april 2006. More than 700.000 domain names were registered during the first 4 hours. After one hour MINA had handled more than 0.5 million SSL connections.
+
+> We found the speed and stability of MINA to be excellent. And although we are still using MINA 0.8.1, we found the API very elegant and easy.
+
+__Frédéric Brégier__ says:
+
+> MINA helped us to get the network layout of OpenLSD done in about 2 months, saving us about 9 months to 1 year of development and fine-grained testing, so we were able to focus on our problem; Open Legacy Storage Document, a framework for document archiving in a huge storage. OpenLSD brings security, network layout, JDBC, and good performance, and allows at least 2 petabytes of documents (2000 terabytes, the limit is virtually 2^192 bytes).
+
+> Our benchmark test went well with massive import capacity (through network with multiple processes) of 1400 documents per second, network (web) retrieves of 1000 documents per second with small latency. Network (MINA) was not the bottleneck so we were able to focus mainly on database optimization. For the web interface, our Tomcat web application connected to OpenLSD Server using pool of MINA connections almost like a JDBC pool.
+
+> Any MINA problems were resolved very quickly either by a quick fix in MINA source code (a few) or by code fix with the support of the MINA mailing list. This was one reason of this success. Therefore we will continue to use MINA on other related project (email archiving and mimic of a professional file transfer monitor). Again, MINA is helping us to
+focus on what the applications need to do and not too much on network layout.
+
+__Alex Burmester__ says:
+
+> We are using MINA at a telco to route low level protocol packets to a third party. We already had a SOAP and also a CORBA interface but for speed purposes we are trying out a lower level protocol and we needed a gateway of sorts to route messages between our cluster of servers and the third party's servers.
+
+> I had been planning on using NIO and some aspects of SEDA but finding MINA was a real treat as it saved a lot of time, is well written and gets more testing than our in house QA would be able to cover. The speed and stability of our app on top of MINA has been excellent.
+
+__Nicholas Clare__ says:
+
+> We use MINA as a networking library to handle concurrent connections to our text based communication server. MINA has worked like a charm. It makes writing server applications simple and is much easier to use than Java's NIO libraries. Because of MINA's stability and ease of use, we plan on using MINA more in our future projects.
+
+__Jean-François Daune__ says:
+
+> We use MINA to communicate with [Banksys](http://www.banksys.com/) 'point of sale' terminals (Visa, Mastercard...) for technical management operations. (software upgrade, remote monitoring, log transfer...)
+
+> So far, MINA has worked really well for us. We used Netty2, and clearly saw the improvements in MINA. I like the MINA API more. MINA really makes it easier to write applications using NIO.
+
+__Luke Hubbard__ says:
+
+> We are using it for the network layer of [Red5](http://www.osflash.org/red5), an open source flash server. At the moment we have RTMP and AMF working and hope to add more protocols in the future. MINA's design and ease of use has helped us get a prototype up and running quickly.
+
+__Thomas Muller__ says:
+
+> What a fantastic API! Definitely the best I've seen since [Doug Lea's Concurrency API](http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html).
+
+__Paolo Perrucci__ says:
+
+> We are using MINA to build the network layer of our multiplayer game server at [Leonardo.it](http://ludonet.leonardo.it/). Using MINA, we implemented different protocols in a few days; Game and HTTP tunneling. In the past, we used NIO, and the advantage of using MINA is evident; the MINA API is elegant and very simple to use. Last, but not least, MINA have a really responsive support.
+
+__Frederic Soulier__ says:
+
+> In 3 days, starting from scratch (knowing nothing about MINA) and with help from this list, I've re-implemented something that took us 2+ months to develop! I've thrown 4000 concurrent connections at it without a problem. The only problem I faced was to increase the limit for open files on my linux box (default was 1024).
+
+__Niklas Therning__ says:
+
+> [SpamDrain](http://www.spamdrain.net/), our online anti-spam service, has been using MINA since late 2005. So far we have developed custom proxies for the POP3, IMAP and SMTP protocols on top of the MINA API. Before MINA we used our own Java NIO abstraction layer which had some serious stability problems. With MINA we haven't experienced any stability issues and the MINA API has really helped us write cleaner code. I just love the way MINA helps you separate the decoding and encoding of protocol messages from the implementation of the protocol's state machine. Other features, like SSLFilter which gives you SSL support virtually without any effort, are also very much appreciated.
+
+__Julien Vermillard__ says:
+
+> I'm using MINA for supervisory control and data acquisition (SCADA) embedded application. It's used for several tasks; connecting supervision clients to the server, interaction of the server with different hardware (other SCADA systems, media stream matrix, programmable automaton, remote data acquisition systems), custom replication protocols for fail-over service. I found MINA when I started implementation using NIO and it was a great time saver. You can switch from RS232 to TCP/IP and add SSL connectivity easily. The stability and the support is really great. The code and the design are simple and efficient, so you can easily implement high quality protocol logic without bothering with all the NIO quirks. I didn't really tested the maximum performance you can get out of MINA, but all I can say is that MINA is running 24/7 with an amazing stability and I'm not afraid of using it in harsh environment.
+
+[__Ashish Paliwal__](http://www.ashishpaliwal.com/blog) says:
+
+> Used Apache MINA for Building a Trap Receiver
+
+> see [White Paper](http://www.hsc.com/HSFiles/Wpos/WhitePaper_Trap_Receiver_using_Apache_MINA.pdf)
+
+__Emmanuel Lecharny__ says:
+
+> MINA handles the following protocols in ADS :
+
+> * LDAP
+> * DNS
+> * NTP
+> * DHCP
+> * Kerberos
+> We also use it to manage replication (using a specific protocol to communicate between two LDAP server). A LDAP client is being drafted atm, using MINA 2.0 too.
+> We are using 1.1.7 currently, but a migration to 2.0 is ready (and we will switch as soon as 2.0.0-M4 will be released)
+
+__Dan Creswell__ says:
+
+> I've used it to build:
+
+> 1. A framework for Paxos consensus
+> 2. A remote transport for a JavaSpace
+> 3. A transport for various gossip-based protocols
+
+__Matthew Estes__ says:
+
+> I'm using it for an asynchronous messaging framework (think RPC/RMI), which
+> is mostly done, but needs documenting and clean up. I also plan to use it
+> to for the HTTP part of a web framework/container. Most of my work is/will
+> be Apache 2.0 licensed open source
+
+__Kevin Williams__ says:
+
+> We used Mina to build an internal distributed coherent cache system
+
+__Matthew Phillips__ says:
+
+> The Avis event notification router and client library uses MINA.
+
+> [Avis](http://avis.sourceforge.net/)
Modified: mina/site/trunk/templates/header.html
URL: http://svn.apache.org/viewvc/mina/site/trunk/templates/header.html?rev=1391063&r1=1391062&r2=1391063&view=diff
==============================================================================
--- mina/site/trunk/templates/header.html (original)
+++ mina/site/trunk/templates/header.html Thu Sep 27 15:51:46 2012
@@ -17,7 +17,7 @@
-->
<html>
<head>
- <title>{% block title %}{{ headers.title }}{% endblock %} — Apache Directory</title>
+ <title>{% block title %}{{ headers.title }}{% endblock %} — Apache MINA</title>
{% block css %}
<link href="{{base}}css/common.css" rel="stylesheet" type="text/css"/>
<link href="{{base}}css/mina.css" rel="stylesheet" type="text/css"/>