This is an automated email from the ASF dual-hosted git repository.
elecharny pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/mina-site.git
The following commit(s) were added to refs/heads/master by this push:
new 34c9a98 Fixed some brokern links
34c9a98 is described below
commit 34c9a98c646dae332e5b6de22819da7351741296
Author: emmanuel lecharny <elecha...@apache.org>
AuthorDate: Mon Nov 1 00:32:22 2021 +0100
Fixed some brokern links
---
source/mina-project/road-map.md | 2 +-
.../mina-project/userguide/ch2-basics/ch2.3-sample-tcp-client.md | 8 ++++----
.../mina-project/userguide/ch2-basics/ch2.4-sample-udp-server.md | 6 +++---
.../mina-project/userguide/ch2-basics/ch2.5-sample-udp-client.md | 2 +-
source/mina-project/userguide/ch3-service/ch3.1-io-service.md | 4 ++--
source/mina-project/userguide/ch5-filters/ch5-filters.md | 2 +-
.../mina-project/userguide/ch6-transports/ch6.1-apr-transport.md | 2 +-
source/mina-project/userguide/ch8-iobuffer/ch8-iobuffer.md | 2 +-
.../mina-project/userguide/ch9-codec-filter/ch9-codec-filter.md | 2 +-
9 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/source/mina-project/road-map.md b/source/mina-project/road-map.md
index 454af3f..1421107 100644
--- a/source/mina-project/road-map.md
+++ b/source/mina-project/road-map.md
@@ -16,7 +16,7 @@ In June 2004, I released a network application framework,
'Netty2'. It was the f
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.
-Meanwhile around 2003 at Apache Directory, Alex Karasulu was wrestling with a
network application framework he developed based on the [Matt Welsh's SEDA
(Staged Event Driven
Architecture)](http://www.eecs.harvard.edu/~mdw/proj/seda/). After several
iterations Alex realized it was very difficult to manage, and started to
research other network application frameworks looking for a replacement. He
wanted something for Java that would scale like SEDA yet was simple to use like
[ACE](http:/ [...]
+Meanwhile around 2003 at Apache Directory, Alex Karasulu was wrestling with a
network application framework he developed based on the [Matt Welsh's SEDA
(Staged Event Driven Architecture)](http://www.sosp.org/2001/papers/welsh.pdf).
After several iterations Alex realized it was very difficult to manage, and
started to research other network application frameworks looking for a
replacement. He wanted something for Java that would scale like SEDA yet was
simple to use like [ACE](http://w [...]
In September 2004, I formally joined the Apache Directory team. Alex and I
decided to mix concepts between the two architectures to create a new network
application framework. We exchanged various ideas to extract the strengths of
both legacy frameworks to ultimately come up with what is today's 'MINA'.
diff --git
a/source/mina-project/userguide/ch2-basics/ch2.3-sample-tcp-client.md
b/source/mina-project/userguide/ch2-basics/ch2.3-sample-tcp-client.md
index c252dd8..f2ab217 100644
--- a/source/mina-project/userguide/ch2-basics/ch2.3-sample-tcp-client.md
+++ b/source/mina-project/userguide/ch2-basics/ch2.3-sample-tcp-client.md
@@ -13,7 +13,7 @@ navNextText: 2.4 - Sample UDP Server
We have seen the Client Architecture. Lets explore a sample Client
implementation.
-We shall use [Sumup
Client](http://mina.apache.org/mina-project/xref/org/apache/mina/example/sumup/Client.html)
as a reference implementation.
+We shall use [Sumup
Client](https://nightlies.apache.org/mina/mina/2.0.22/xref/org/apache/mina/example/sumup/Client.html)
as a reference implementation.
We will remove boiler plate code and concentrate on the important constructs.
Below the code for the Client :
@@ -90,7 +90,7 @@ We add Filters to the Filter Chain for the Connector. Here we
have added a Proto
connector.setHandler(new ClientSessionHandler(values));
```
-Here we create an instance of
[ClientSessionHandler](http://mina.apache.org/mina-project/xref/org/apache/mina/example/sumup/ClientSessionHandler.html)
and set it as a handler for the Connector.
+Here we create an instance of
[ClientSessionHandler](https://nightlies.apache.org/mina/mina/2.0.22/xref/org/apache/mina/example/sumup/ClientSessionHandler.html)
and set it as a handler for the Connector.
## Bind to Server
@@ -111,5 +111,5 @@ for (;;) {
}
```
-Here is the most important stuff. We connect to remote Server. Since, connect
is an async task, we use the
[ConnectFuture](http://mina.apache.org/mina-project/xref/org/apache/mina/core/future/ConnectFuture.html)
class to know the when the connection is complete.
-Once the connection is complete, we get the associated
[IoSession](http://mina.apache.org/mina-project/xref/org/apache/mina/core/session/IoSession.html).
To send any message to the Server, we shall have to write to the session. All
responses/messages from server shall traverse the Filter chain and finally be
handled in IoHandler.
+Here is the most important stuff. We connect to remote Server. Since, connect
is an async task, we use the
[ConnectFuture](https://nightlies.apache.org/mina/mina/2.0.22/xref/org/apache/mina/core/future/ConnectFuture.html)
class to know the when the connection is complete.
+Once the connection is complete, we get the associated
[IoSession](https://nightlies.apache.org/mina/mina/2.0.22/xref/org/apache/mina/core/session/IoSession.html).
To send any message to the Server, we shall have to write to the session. All
responses/messages from server shall traverse the Filter chain and finally be
handled in IoHandler.
diff --git
a/source/mina-project/userguide/ch2-basics/ch2.4-sample-udp-server.md
b/source/mina-project/userguide/ch2-basics/ch2.4-sample-udp-server.md
index 938e887..5e1b828 100644
--- a/source/mina-project/userguide/ch2-basics/ch2.4-sample-udp-server.md
+++ b/source/mina-project/userguide/ch2-basics/ch2.4-sample-udp-server.md
@@ -11,12 +11,12 @@ navNextText: 2.5 - Sample UDP Client
# 2.4 - Sample UDP Server
-We will begin by looking at the code found in the
[org.apache.mina.example.udp](http://mina.apache.org/mina-project/xref/org/apache/mina/example/udp/package-summary.html)
package. To keep life simple, we shall concentrate on MINA related constructs
only.
+We will begin by looking at the code found in the
[org.apache.mina.example.udp](https://nightlies.apache.org/mina/mina/2.0.22/xref/org/apache/mina/example/udp/package-summary.html)
package. To keep life simple, we shall concentrate on MINA related constructs
only.
To construct the server, we shall have to do the following:
-1. Create a Datagram Socket to listen for incoming Client requests (See
[MemoryMonitor.java](http://mina.apache.org/mina-project/xref/org/apache/mina/example/udp/MemoryMonitor.html))
-2. Create an IoHandler to handle the MINA framework generated events (See
[MemoryMonitorHandler.java](http://mina.apache.org/mina-project/xref/org/apache/mina/example/udp/MemoryMonitorHandler.html))
+1. Create a Datagram Socket to listen for incoming Client requests (See
[MemoryMonitor.java](https://nightlies.apache.org/mina/mina/2.0.22/xref/org/apache/mina/example/udp/MemoryMonitor.html))
+2. Create an IoHandler to handle the MINA framework generated events (See
[MemoryMonitorHandler.java](https://nightlies.apache.org/mina/mina/2.0.22/xref/org/apache/mina/example/udp/MemoryMonitorHandler.html))
Here is the first snippet that addresses Point# 1:
diff --git
a/source/mina-project/userguide/ch2-basics/ch2.5-sample-udp-client.md
b/source/mina-project/userguide/ch2-basics/ch2.5-sample-udp-client.md
index 13f48d4..4a2c3c1 100644
--- a/source/mina-project/userguide/ch2-basics/ch2.5-sample-udp-client.md
+++ b/source/mina-project/userguide/ch2-basics/ch2.5-sample-udp-client.md
@@ -20,7 +20,7 @@ To implement the Client we need to do following:
* Collect free memory
* Send the Data to the Server
-We will begin by looking at the file
[MemMonClient.java](http://mina.apache.org/mina-project/xref/org/apache/mina/example/udp/client/MemMonClient.html),
found in the org.apache.mina.example.udp.client java package. The first few
lines of the code are simple and straightforward.
+We will begin by looking at the file
[MemMonClient.java](https://nightlies.apache.org/mina/mina/2.0.22/xref/org/apache/mina/example/udp/client/MemMonClient.html),
found in the org.apache.mina.example.udp.client java package. The first few
lines of the code are simple and straightforward.
```java
connector = new NioDatagramConnector();
diff --git a/source/mina-project/userguide/ch3-service/ch3.1-io-service.md
b/source/mina-project/userguide/ch3-service/ch3.1-io-service.md
index c8431e8..6a23e10 100644
--- a/source/mina-project/userguide/ch3-service/ch3.1-io-service.md
+++ b/source/mina-project/userguide/ch3-service/ch3.1-io-service.md
@@ -11,11 +11,11 @@ navNextText: 3.2 - IoService Details
# 3.1 - IoService Introduction
-[IoService](http://mina.apache.org/mina-project/xref/org/apache/mina/core/service/IoService.html)
provides basic **I/O** Service and manages **I/O** Sessions within **MINA**.
Its one of the most crucial part of **MINA** Architecture. The implementing
classes of _IoService_ and child interface, are where most of the low level
**I/O** operations are handled.
+[IoService](https://nightlies.apache.org/mina/mina/2.0.22/xref/org/apache/mina/core/service/IoService.html)
provides basic **I/O** Service and manages **I/O** Sessions within **MINA**.
Its one of the most crucial part of **MINA** Architecture. The implementing
classes of _IoService_ and child interface, are where most of the low level
**I/O** operations are handled.
# IoService Mind Map
-Let's try to see what are the responsibilities of the _IoService_ and it
implementing class
[AbstractIoService](http://mina.apache.org/mina-project/xref/org/apache/mina/core/service/AbstractIoService.html).
Let's take a slightly different approach of first using a [Mind
Map](http://en.wikipedia.org/wiki/Mind_map) and then jump into the inner
working. The Mind Map was created using [XMind](http://www.xmind.net/).
+Let's try to see what are the responsibilities of the _IoService_ and it
implementing class
[AbstractIoService](https://nightlies.apache.org/mina/mina/2.0.22/xref/org/apache/mina/core/service/AbstractIoService.html).
Let's take a slightly different approach of first using a [Mind
Map](http://en.wikipedia.org/wiki/Mind_map) and then jump into the inner
working. The Mind Map was created using [XMind](http://www.xmind.net/).
diff --git a/source/mina-project/userguide/ch5-filters/ch5-filters.md
b/source/mina-project/userguide/ch5-filters/ch5-filters.md
index 291a401..0f7d940 100644
--- a/source/mina-project/userguide/ch5-filters/ch5-filters.md
+++ b/source/mina-project/userguide/ch5-filters/ch5-filters.md
@@ -140,7 +140,7 @@ private static class MyByteBuffer extends ByteBufferProxy {
}
```
-If you are using MINA 2.0, it will be somewhat different from 1.0 and 1.1.
Please refer to
[CompressionFilter](http://mina.apache.org/mina-project/xref/org/apache/mina/filter/compression/CompressionFilter.html)
and
[RequestResponseFilter](http://mina.apache.org/mina-project/xref/org/apache/mina/filter/reqres/RequestResponseFilter.html)
meanwhile.
+If you are using MINA 2.0, it will be somewhat different from 1.0 and 1.1.
Please refer to
[CompressionFilter](https://nightlies.apache.org/mina/mina/2.0.22/xref/org/apache/mina/filter/compression/CompressionFilter.html)
and
[RequestResponseFilter](https://nightlies.apache.org/mina/mina/2.0.22/xref/org/apache/mina/filter/reqres/RequestResponseFilter.html)
meanwhile.
## Be Careful When Filtering sessionCreated Event
diff --git
a/source/mina-project/userguide/ch6-transports/ch6.1-apr-transport.md
b/source/mina-project/userguide/ch6-transports/ch6.1-apr-transport.md
index 9ccb29f..4005582 100644
--- a/source/mina-project/userguide/ch6-transports/ch6.1-apr-transport.md
+++ b/source/mina-project/userguide/ch6-transports/ch6.1-apr-transport.md
@@ -26,7 +26,7 @@ navNextText: 6.2 - Serial Transport
## Using APR Transport
-Refer [Time
Server](https://mina.apache.org/mina-project/xref/org/apache/mina/example/gettingstarted/timeserver/)
example for complete source
+Refer [Time
Server]https://nightlies.apache.org/mina/mina/2.0.22/xref/org/apache/mina/example/gettingstarted/timeserver/)
example for complete source
Lets see how NIO based Time server implementation looks like
diff --git a/source/mina-project/userguide/ch8-iobuffer/ch8-iobuffer.md
b/source/mina-project/userguide/ch8-iobuffer/ch8-iobuffer.md
index 383ef8a..9e58880 100644
--- a/source/mina-project/userguide/ch8-iobuffer/ch8-iobuffer.md
+++ b/source/mina-project/userguide/ch8-iobuffer/ch8-iobuffer.md
@@ -43,7 +43,7 @@ The allocate() method takes one or two arguments. The first
form takes two argum
* __capacity__ - the capacity of the buffer
* __direct__ - type of buffer. true to get direct buffer, false to get heap
buffer
-The default buffer allocation is handled by
[SimpleBufferAllocator](http://mina.apache.org/mina-project/xref/org/apache/mina/core/buffer/SimpleBufferAllocator.html)
+The default buffer allocation is handled by
[SimpleBufferAllocator](https://nightlies.apache.org/mina/mina/2.0.22/xref/org/apache/mina/core/buffer/SimpleBufferAllocator.html)
Alternatively, following form can also be used
diff --git a/source/mina-project/userguide/ch9-codec-filter/ch9-codec-filter.md
b/source/mina-project/userguide/ch9-codec-filter/ch9-codec-filter.md
index ac779ec..b0ddf37 100644
--- a/source/mina-project/userguide/ch9-codec-filter/ch9-codec-filter.md
+++ b/source/mina-project/userguide/ch9-codec-filter/ch9-codec-filter.md
@@ -120,7 +120,7 @@ Remarks:
* MINA will call the encode function for all messages in the IoSession's write
queue. Since our client will only write ImageRequest objects, we can safely
cast message to ImageRequest.
* We allocate a new IoBuffer from the heap. It's best to avoid using direct
buffers, since generally heap buffers perform better.
see <http://issues.apache.org/jira/browse/DIRMINA-289>)
-* You do not have to release the buffer, MINA will do it for you, see
<http://mina.apache.org/mina-project/apidocs/org/apache/mina/core/buffer/IoBuffer.html>
+* You do not have to release the buffer, MINA will do it for you, see
<https://nightlies.apache.org/mina/mina/2.0.22/apidocs/org/apache/mina/core/buffer/IoBuffer.html>
* In the dispose() method you should release all resources acquired during
encoding for the specified session. If there is nothing to dispose you could
let your encoder inherit from ProtocolEncoderAdapter.
Now let's have a look at the decoder. The CumulativeProtocolDecoder is a great
help for writing your own decoder: it will buffer all incoming data until your
decoder decides it can do something with it.
