svn commit: r997806 - in /websites/staging/mina/trunk/content: ./ mina-project/userguide/ mina-project/userguide/ch4-session/

[buildbot]

Author: buildbot
Date: Tue Sep 20 09:16:49 2016
New Revision: 997806

Log:
Staging update by buildbot for mina

Added:

websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4.1-session-configuration.html

websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4.2-session-statistics.html
Modified:
websites/staging/mina/trunk/content/   (props changed)

websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html

websites/staging/mina/trunk/content/mina-project/userguide/user-guide-toc.html

Propchange: websites/staging/mina/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Tue Sep 20 09:16:49 2016
@@ -1 +1 @@
-1758403
+1761541

Modified: 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
==
--- 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
 (original)
+++ 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
 Tue Sep 20 09:16:49 2016
@@ -182,8 +182,20 @@ h2:hover > .headerlink, h3:hover > .head
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, 
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, 
dt:hover > .elementid-permalink { visibility: visible }
 Chapter 4 - Session¶
-The Session is at the heart of MINA : every time a client connects to the 
server, a new session is created, and will be kept in memory until the client 
is disconnected.
-A session is used to store persistent informations about the connection, 
plus any kind of information the server might need to use during the request 
processing, and eventually during the whole session life.
+Content¶
+
+Chapter 4.1 - Session 
Configuration
+Chapter 4.2 - Session 
Statistics
+
+The Session is at the heart of MINA : every time a client connects to the 
server, a new session is created on the server, and will be kept in memory 
until the client is disconnected. If you are using MINA on the client side, 
everytime you conect to a server, a session will be created on the client 
too.
+A session is used to store persistent informations about the connection, 
plus any kind of information the client or the server might need to use during 
the request processing, and eventually during the whole session life.
+This is also your access point for any operation you need to do on a 
session : sending messages, closing the session, etc...
+
+It is critical to understand that due to the asynchrnous very nature of NIO, 
reading from a session does not make a lot of sense. Actually, your application 
get signalled whe some incoming message has arrived, and this is the IoHandler 
which is responsible for handling such event.
+
+In other words, don't call session.read(). Never.
+
+
 Session state¶
 A session has a state, which will evolve during time.
 
@@ -195,10 +207,60 @@ h2:hover > .headerlink, h3:hover > .head
 
 
 Closing : the session is being closed (the remaining messages are being 
flushed, cleaning up is not terminated)
-Closed : The session is now closed, nothing else can be done to revive 
it.
+Closed : The session is now closed, nothing else can be done to revive it. 
This is actually not a real state : when teh session is closed, it's 
removed.
 
 The following state diagram exposes all the possible states and transitions 
:
 
+We have a set of methods to get some information about the session 
status.
+Session status :
+
+isActive() : tells if the session is valid (it might mean different things 
depending on the implementation)
+isClosing() : tells if the session is already being closed
+isConnected() : tells if the session is active (ie, not in the closing 
mode)
+
+Opening a session¶
+Actually, there is nothing you have to do : it's automatic ! Everytime a 
remote peer connect to a server, the server will create a new connection. On 
the client side, everytime you connect to a server, a session will be 
created.
+This session is passed as an argument to your handler, so that you can do 
something with it in your application. On the client side, when you do connect 
to a server, you can get back the created session this way :
+:::java
+...
+ConnectFuture connectionFuture = connector.connect(address);
+connectionFuture.awaitUninterruptibly();
+if (!connectionFuture.isConnected()) 
{
+return false;
+}
+
+session = connectionFuture.getSession();
+...
+
+
+
+You can also do it in a shortest way :
+:::java
+...
+session = connector.connect(address).getSession();
+...
+Initialization¶
+When a new session is created, it has to be initialized. This is done using 
the default IoService configuration, bt you can update this configuration later 
on. Actually, when the session is created, we internally create a copy 

svn commit: r1761541 - in /mina/site/trunk/content/mina-project/userguide: ch4-session/ch4-session.mdtext ch4-session/ch4.1-session-configuration.mdtext ch4-session/ch4.2-session-statistics.mdtext use

[elecharny]

Author: elecharny
Date: Tue Sep 20 09:16:40 2016
New Revision: 1761541

URL: http://svn.apache.org/viewvc?rev=1761541&view=rev
Log:
Added some pages related to session

Added:

mina/site/trunk/content/mina-project/userguide/ch4-session/ch4.1-session-configuration.mdtext
   (with props)

mina/site/trunk/content/mina-project/userguide/ch4-session/ch4.2-session-statistics.mdtext
   (with props)
Modified:

mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext
mina/site/trunk/content/mina-project/userguide/user-guide-toc.mdtext

Modified: 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext
URL: 
http://svn.apache.org/viewvc/mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext?rev=1761541&r1=1761540&r2=1761541&view=diff
==
--- 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext 
(original)
+++ 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext 
Tue Sep 20 09:16:40 2016
@@ -24,9 +24,22 @@ Notice:Licensed to the Apache Softwa
 
 # Chapter 4 - Session
 
-The Session is at the heart of MINA : every time a client connects to the 
server, a new session is created, and will be kept in memory until the client 
is disconnected.
+## Content
 
-A session is used to store persistent informations about the connection, plus 
any kind of information the server might need to use during the request 
processing, and eventually during the whole session life.
+1. [Chapter 4.1 - Session Configuration](ch4.1-session-configuration.html)
+1. [Chapter 4.2 - Session Statistics](ch4.2-session-statistics.html)
+
+The Session is at the heart of MINA : every time a client connects to the 
server, a new session is created on the server, and will be kept in memory 
until the client is disconnected. If you are using MINA on the client side, 
everytime you conect to a server, a session will be created on the client too.
+
+A session is used to store persistent informations about the connection, plus 
any kind of information the client or the server might need to use during the 
request processing, and eventually during the whole session life.
+
+This is also your access point for any operation you need to do on a session : 
sending messages, closing the session, etc...
+
+
+It is critical to understand that due to the asynchrnous very nature of NIO, 
reading from a session does not make a lot of sense. Actually, your application 
get signalled whe some incoming message has arrived, and this is the IoHandler 
which is responsible for handling such event.
+
+In other words, don't call session.read(). Never.
+
 
 ## Session state
 
@@ -38,12 +51,84 @@ A session has a state, which will evolve
 * Idle for write : no write has actually been made for a period of time
 * Idle for both : no read nor write for a period of time
 * Closing : the session is being closed (the remaining messages are being 
flushed, cleaning up is not terminated)
-* Closed : The session is now closed, nothing else can be done to revive it.
+* Closed : The session is now closed, nothing else can be done to revive it. 
This is actually not a real state : when teh session is closed, it's removed.
 
 The following state diagram exposes all the possible states and transitions :
 
 ![](../../../staticresources/images/mina/session-state.png)
 
+We have a set of methods to get some information about the session status.
+
+Session status :
+
+* isActive() : tells if the session is valid (it might mean different things 
depending on the implementation)
+* isClosing() : tells if the session is already being closed
+* isConnected() : tells if the session is active (ie, not in the closing mode)
+
+## Opening a session
+
+Actually, there is nothing you have to do : it's automatic ! Everytime a 
remote peer connect to a server, the server will create a new connection. On 
the client side, everytime you connect to a server, a session will be created.
+
+This session is passed as an argument to your handler, so that you can do 
something with it in your application. On the client side, when you do connect 
to a server, you can get back the created session this way :
+
+  :::java
+...
+ConnectFuture connectionFuture = connector.connect(address);
+connectionFuture.awaitUninterruptibly();
+
+if (!connectionFuture.isConnected()) {
+return false;
+}
+
+session = connectionFuture.getSession();
+...
+
+You can also do it in a shortest way :
+
+  :::java
+...
+session = connector.connect(address).getSession();
+...
+
+## Initialization
+
+When a new session is created, it has to be initialized. This is done using 
the default IoService configuration, bt you can update this configuration later 
on. Actually, when the session is created, we internally create a copy of the 
default IoService configuration that is stored wit

svn commit: r997864 - in /websites/staging/mina/trunk/content: ./ mina-project/userguide/ch4-session/ch4-session.html

[buildbot]

Author: buildbot
Date: Tue Sep 20 21:53:45 2016
New Revision: 997864

Log:
Staging update by buildbot for mina

Modified:
websites/staging/mina/trunk/content/   (props changed)

websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html

Propchange: websites/staging/mina/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Tue Sep 20 21:53:45 2016
@@ -1 +1 @@
-1761541
+1761643

Modified: 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
==
--- 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
 (original)
+++ 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
 Tue Sep 20 21:53:45 2016
@@ -221,24 +221,26 @@ In other words, don't call session.read(
 Opening a session¶
 Actually, there is nothing you have to do : it's automatic ! Everytime a 
remote peer connect to a server, the server will create a new connection. On 
the client side, everytime you connect to a server, a session will be 
created.
 This session is passed as an argument to your handler, so that you can do 
something with it in your application. On the client side, when you do connect 
to a server, you can get back the created session this way :
-:::java
-...
-ConnectFuture connectionFuture = connector.connect(address);
-connectionFuture.awaitUninterruptibly();
-if (!connectionFuture.isConnected()) 
{
-return false;
-}
+...
+ConnectFuture connectionFuture 
= connector.connect(address);
+connectionFuture.awaitUninterruptibly();
 
-session = connectionFuture.getSession();
-...
+if (!connectionFuture.isConnected()) {
+return false;
+}
+
+session = connectionFuture.getSession();
+...
 
 
 
 You can also do it in a shortest way :
-:::java
-...
-session = connector.connect(address).getSession();
-...
+...
+session = connector.connect(address).getSession();
+...
+
+
+
 Initialization¶
 When a new session is created, it has to be initialized. This is done using 
the default IoService configuration, bt you can update this configuration later 
on. Actually, when the session is created, we internally create a copy of the 
default IoService configuration that is stored within the session, and this is 
this configuration instance that will be used (and that can be modified).
 This initialization will also starts the statistics counters, create the 
Attributes container, associate a write queue to to the session (this is where 
the messages will be enqueued until they have been sent), and ultimately, would 
you have provided a specific task to do during this phase, it will call it.
@@ -305,17 +307,15 @@ Be aware that if the remote peer is not
 
 
 and here is the factory interface we can implement if we want to define 
another kind of container :
-public interface IoSessionDataStructureFactory {
-/**
- * Returns an {@link IoSessionAttributeMap} which is going to be associated
- * with the specified session.  Please note that the returned
- * implementation must be thread-safe.
- */
- IoSessionAttributeMap getAttributeMap(IoSession session) throws Exception;
- }
-
-
-
+:::java
+public interface IoSessionDataStructureFactory {
+/*
+ * Returns an {@link IoSessionAttributeMap} which is going to be 
associated
+ * with the specified session.  Please note that the returned
+ * implementation must be thread-safe.
+ /
+ IoSessionAttributeMap getAttributeMap(IoSession session) throws 
Exception;
+ }
 The session attributes access¶
 There are many methods available to manipulate the session's attributes 
:
 

svn commit: r1761643 - /mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext

[elecharny]

Author: elecharny
Date: Tue Sep 20 21:53:39 2016
New Revision: 1761643

URL: http://svn.apache.org/viewvc?rev=1761643&view=rev
Log:
Fixed the formating

Modified:

mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext

Modified: 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext
URL: 
http://svn.apache.org/viewvc/mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext?rev=1761643&r1=1761642&r2=1761643&view=diff
==
--- 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext 
(original)
+++ 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext 
Tue Sep 20 21:53:39 2016
@@ -71,7 +71,7 @@ Actually, there is nothing you have to d
 
 This session is passed as an argument to your handler, so that you can do 
something with it in your application. On the client side, when you do connect 
to a server, you can get back the created session this way :
 
-  :::java
+:::java
 ...
 ConnectFuture connectionFuture = connector.connect(address);
 connectionFuture.awaitUninterruptibly();
@@ -85,7 +85,7 @@ This session is passed as an argument to
 
 You can also do it in a shortest way :
 
-  :::java
+:::java
 ...
 session = connector.connect(address).getSession();
 ...
@@ -151,7 +151,7 @@ It might be necessary to store some data
 
 For instance, if you want to track the number of request a user has sent since 
the session has been created, it's easy to store it into this map: just create 
a key that will be associated with this value.
 
-   :::java
+:::java
 ...
 int counterValue = session.getAttribute( "counter" );
 session.setAttribute( "counter", counterValue + 1 );
@@ -185,6 +185,7 @@ This snippet of code shows how the conta
 
 and here is the factory interface we can implement if we want to define 
another kind of container :
 
+  :::java
public interface IoSessionDataStructureFactory {
/**
 * Returns an {@link IoSessionAttributeMap} which is going to 
be associated
@@ -210,6 +211,7 @@ There are many methods available to mani
 * Object setAttributeIfAbsent(Object key) : adds a new attribute with no 
value, if it does not already exist
 * Object setAttributeIfAbsent(Object key, Object value) : adds a new 
attribute/value pair, if it does not already exist
 
+
 All those methods allows your application to store, remove, get or update the 
attributes stored into your session. Also note that some attributes are used 
internally by MINA : don't lightly modify those you didn't create !
 
 ## Filter chain

svn commit: r1761644 - /mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext

[elecharny]

Author: elecharny
Date: Tue Sep 20 21:55:06 2016
New Revision: 1761644

URL: http://svn.apache.org/viewvc?rev=1761644&view=rev
Log:
Fixed the formating

Modified:

mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext

Modified: 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext
URL: 
http://svn.apache.org/viewvc/mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext?rev=1761644&r1=1761643&r2=1761644&view=diff
==
--- 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext 
(original)
+++ 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext 
Tue Sep 20 21:55:06 2016
@@ -168,32 +168,32 @@ As we said, this container is a key/valu
 
 This snippet of code shows how the container is created during the session 
initialization :
 
-   :::java
-   protected final void initSession(IoSession session,
-IoFuture future, IoSessionInitializer sessionInitializer) {
-...
-try {
-((AbstractIoSession) session).setAttributeMap(session.getService()
-
.getSessionDataStructureFactory().getAttributeMap(session));
-} catch (IoSessionInitializationException e) {
-throw e;
-} catch (Exception e) {
-throw new IoSessionInitializationException(
-"Failed to initialize an attributeMap.", e);
-}
-...
+   :::java
+   protected final void initSession(IoSession session,
+  IoFuture future, IoSessionInitializer sessionInitializer) {
+  ...
+  try {
+  ((AbstractIoSession) 
session).setAttributeMap(session.getService()
+  
.getSessionDataStructureFactory().getAttributeMap(session));
+  } catch (IoSessionInitializationException e) {
+  throw e;
+  } catch (Exception e) {
+  throw new IoSessionInitializationException(
+  "Failed to initialize an attributeMap.", e);
+  }
+  ...
 
 and here is the factory interface we can implement if we want to define 
another kind of container :
 
-  :::java
-   public interface IoSessionDataStructureFactory {
-   /**
-* Returns an {@link IoSessionAttributeMap} which is going to 
be associated
-* with the specified session.  Please note that the 
returned
-* implementation must be thread-safe.
-*/
-IoSessionAttributeMap getAttributeMap(IoSession session) 
throws Exception;
-}
+:::java
+public interface IoSessionDataStructureFactory {
+  /**
+  * Returns an {@link IoSessionAttributeMap} which is going to be 
associated
+  * with the specified session.  Please note that the returned
+  * implementation must be thread-safe.
+  */
+  IoSessionAttributeMap getAttributeMap(IoSession session) throws 
Exception;
+}
 
 ### The session attributes access
 

svn commit: r997865 - in /websites/staging/mina/trunk/content: ./ mina-project/userguide/ch4-session/ch4-session.html

[buildbot]

Author: buildbot
Date: Tue Sep 20 21:55:11 2016
New Revision: 997865

Log:
Staging update by buildbot for mina

Modified:
websites/staging/mina/trunk/content/   (props changed)

websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html

Propchange: websites/staging/mina/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Tue Sep 20 21:55:11 2016
@@ -1 +1 @@
-1761643
+1761644

Modified: 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
==
--- 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
 (original)
+++ 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
 Tue Sep 20 21:55:11 2016
@@ -291,31 +291,33 @@ Be aware that if the remote peer is not
 As we said, this container is a key/value container, which default to a 
Map, but it's also possible to define another data structure if one want to 
handle long lived data, or to avoid storing all those data in memory if they 
are large : we can implement an interface and a factory that will be used to 
create this container when the session is created.
 This snippet of code shows how the container is created during the session 
initialization :
 protected final void initSession(IoSession session,
-IoFuture future, IoSessionInitializer sessionInitializer) {
-...
-try {
-((AbstractIoSession) session).setAttributeMap(session.getService()
-.getSessionDataStructureFactory().getAttributeMap(session));
-} catch (IoSessionInitializationException e) {
-throw e;
-} catch (Exception e) {
-throw new IoSessionInitializationException(
-"Failed to initialize an 
attributeMap.", e);
-}
-...
+  IoFuture future, IoSessionInitializer sessionInitializer) {
+  ...
+  try {
+  ((AbstractIoSession) session).setAttributeMap(session.getService()
+  .getSessionDataStructureFactory().getAttributeMap(session));
+  } catch (IoSessionInitializationException e) {
+  throw e;
+  } catch (Exception e) {
+  throw new IoSessionInitializationException(
+  "Failed to initialize an 
attributeMap.", e);
+  }
+  ...
 
 
 
 and here is the factory interface we can implement if we want to define 
another kind of container :
-:::java
-public interface IoSessionDataStructureFactory {
-/*
- * Returns an {@link IoSessionAttributeMap} which is going to be 
associated
- * with the specified session.  Please note that the returned
- * implementation must be thread-safe.
- /
- IoSessionAttributeMap getAttributeMap(IoSession session) throws 
Exception;
- }
+public interface IoSessionDataStructureFactory {
+  /**
+  * Returns an {@link IoSessionAttributeMap} which is going 
to be associated
+  * with the specified session.  Please 
note that the returned
+  * implementation must be thread-safe.
+  */
+  IoSessionAttributeMap getAttributeMap(IoSession session) throws Exception;
+}
+
+
+
 The session attributes access¶
 There are many methods available to manipulate the session's attributes 
:
 

svn commit: r997866 - /websites/staging/mina/trunk/content/

[buildbot]

Author: buildbot
Date: Tue Sep 20 21:56:30 2016
New Revision: 997866

Log:
Staging update by buildbot for mina

Modified:
websites/staging/mina/trunk/content/   (props changed)

Propchange: websites/staging/mina/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Tue Sep 20 21:56:30 2016
@@ -1 +1 @@
-1761644
+1761645

svn commit: r1761645 - /mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext

[elecharny]

Author: elecharny
Date: Tue Sep 20 21:56:25 2016
New Revision: 1761645

URL: http://svn.apache.org/viewvc?rev=1761645&view=rev
Log:
Fixed the formating, again

Modified:

mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext

Modified: 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext
URL: 
http://svn.apache.org/viewvc/mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext?rev=1761645&r1=1761644&r2=1761645&view=diff
==
--- 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext 
(original)
+++ 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext 
Tue Sep 20 21:56:25 2016
@@ -199,17 +199,17 @@ and here is the factory interface we can
 
 There are many methods available to manipulate the session's attributes :
 
-* boolean containsAttribute(Object key) : tells if a given attribute is present
-* Object getAttribute(Object key) : gets the value for a given attribute
-* Object getAttribute(Object key, Object defaultValue) : gets the value for a 
given attribute, or a default value if absent
-* Set getAttributeKeys() : gets the set of all the stored attributes
-* Object removeAttribute(Object key) : remove a given attribute
-* boolean removeAttribute(Object key, Object value) : remove a given 
attribute/value pair
-* boolean replaceAttribute(Object key, Object oldValue, Object newValue) : 
replace a give attribute/value pair
-* Object setAttribute(Object key) : adds a new attribute with no value
-* Object setAttribute(Object key, Object value) : adds a new attribute/value 
pair
-* Object setAttributeIfAbsent(Object key) : adds a new attribute with no 
value, if it does not already exist
-* Object setAttributeIfAbsent(Object key, Object value) : adds a new 
attribute/value pair, if it does not already exist
+  * boolean containsAttribute(Object key) : tells if a given attribute is 
present
+  * Object getAttribute(Object key) : gets the value for a given attribute
+  * Object getAttribute(Object key, Object defaultValue) : gets the value for 
a given attribute, or a default value if absent
+  * Set getAttributeKeys() : gets the set of all the stored attributes
+  * Object removeAttribute(Object key) : remove a given attribute
+  * boolean removeAttribute(Object key, Object value) : remove a given 
attribute/value pair
+  * boolean replaceAttribute(Object key, Object oldValue, Object newValue) : 
replace a give attribute/value pair
+  * Object setAttribute(Object key) : adds a new attribute with no value
+  * Object setAttribute(Object key, Object value) : adds a new attribute/value 
pair
+  * Object setAttributeIfAbsent(Object key) : adds a new attribute with no 
value, if it does not already exist
+  * Object setAttributeIfAbsent(Object key, Object value) : adds a new 
attribute/value pair, if it does not already exist
 
 
 All those methods allows your application to store, remove, get or update the 
attributes stored into your session. Also note that some attributes are used 
internally by MINA : don't lightly modify those you didn't create !

svn commit: r1761646 - /mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext

[elecharny]

Author: elecharny
Date: Tue Sep 20 21:58:38 2016
New Revision: 1761646

URL: http://svn.apache.org/viewvc?rev=1761646&view=rev
Log:
Fixed the formating, again

Modified:

mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext

Modified: 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext
URL: 
http://svn.apache.org/viewvc/mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext?rev=1761646&r1=1761645&r2=1761646&view=diff
==
--- 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext 
(original)
+++ 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext 
Tue Sep 20 21:58:38 2016
@@ -199,17 +199,17 @@ and here is the factory interface we can
 
 There are many methods available to manipulate the session's attributes :
 
-  * boolean containsAttribute(Object key) : tells if a given attribute is 
present
-  * Object getAttribute(Object key) : gets the value for a given attribute
-  * Object getAttribute(Object key, Object defaultValue) : gets the value for 
a given attribute, or a default value if absent
-  * Set getAttributeKeys() : gets the set of all the stored attributes
-  * Object removeAttribute(Object key) : remove a given attribute
-  * boolean removeAttribute(Object key, Object value) : remove a given 
attribute/value pair
-  * boolean replaceAttribute(Object key, Object oldValue, Object newValue) : 
replace a give attribute/value pair
-  * Object setAttribute(Object key) : adds a new attribute with no value
-  * Object setAttribute(Object key, Object value) : adds a new attribute/value 
pair
-  * Object setAttributeIfAbsent(Object key) : adds a new attribute with no 
value, if it does not already exist
-  * Object setAttributeIfAbsent(Object key, Object value) : adds a new 
attribute/value pair, if it does not already exist
+* boolean containsAttribute(Object key) : tells if a given attribute is present
+* Object getAttribute(Object key) : gets the value for a given attribute
+* Object getAttribute(Object key, Object defaultValue) : gets the value for a 
given attribute, or a default value if absent
+* Set getAttributeKeys() : gets the set of all the stored attributes
+* Object removeAttribute(Object key) : remove a given attribute
+* boolean removeAttribute(Object key, Object value) : remove a given 
attribute/value pair
+* boolean replaceAttribute(Object key, Object oldValue, Object newValue) : 
replace a give attribute/value pair
+* Object setAttribute(Object key) : adds a new attribute with no value
+* Object setAttribute(Object key, Object value) : adds a new attribute/value 
pair
+* Object setAttributeIfAbsent(Object key) : adds a new attribute with no 
value, if it does not already exist
+* Object setAttributeIfAbsent(Object key, Object value) : adds a new 
attribute/value pair, if it does not already exist
 
 
 All those methods allows your application to store, remove, get or update the 
attributes stored into your session. Also note that some attributes are used 
internally by MINA : don't lightly modify those you didn't create !
@@ -238,7 +238,9 @@ For further informations about the sessi
 
 Last, not least, a session is attached to a Handler, in charge of dispatching 
the messages to your application. This handler will also send back response by 
using the session, simply by calling the write() method :
 
-   :::java
-   ...
-session.write(  );
+:::java
 ...
+  session.write(  );
+  ...
+
+

svn commit: r997867 - in /websites/staging/mina/trunk/content: ./ mina-project/userguide/ch4-session/ch4-session.html

[buildbot]

Author: buildbot
Date: Tue Sep 20 21:58:43 2016
New Revision: 997867

Log:
Staging update by buildbot for mina

Modified:
websites/staging/mina/trunk/content/   (props changed)

websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html

Propchange: websites/staging/mina/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Tue Sep 20 21:58:43 2016
@@ -1 +1 @@
-1761645
+1761646

Modified: 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
==
--- 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
 (original)
+++ 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
 Tue Sep 20 21:58:43 2016
@@ -350,8 +350,8 @@ Be aware that if the remote peer is not
 Handler¶
 Last, not least, a session is attached to a Handler, in charge of 
dispatching the messages to your application. This handler will also send back 
response by using the session, simply by calling the write() method :
 ...
-session.write(  );
-...
+  session.write(  );
+  ...
 
 
 

svn commit: r997868 - in /websites/staging/mina/trunk/content: ./ mina-project/userguide/ch4-session/ch4-session.html

[buildbot]

Author: buildbot
Date: Tue Sep 20 22:03:00 2016
New Revision: 997868

Log:
Staging update by buildbot for mina

Modified:
websites/staging/mina/trunk/content/   (props changed)

websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html

Propchange: websites/staging/mina/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Tue Sep 20 22:03:00 2016
@@ -1 +1 @@
-1761646
+1761647

Modified: 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
==
--- 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
 (original)
+++ 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
 Tue Sep 20 22:03:00 2016
@@ -324,7 +324,7 @@ Be aware that if the remote peer is not
 boolean containsAttribute(Object key) : tells if a given attribute is 
present
 Object getAttribute(Object key) : gets the value for a given attribute
 Object getAttribute(Object key, Object defaultValue) : gets the value for 
a given attribute, or a default value if absent
-Set getAttributeKeys() : gets the set of all the stored 
attributes
+Set\ getAttributeKeys() : gets the set of all the stored 
attributes
 Object removeAttribute(Object key) : remove a given attribute
 boolean removeAttribute(Object key, Object value) : remove a given 
attribute/value pair
 boolean replaceAttribute(Object key, Object oldValue, Object newValue) : 
replace a give attribute/value pair
@@ -333,6 +333,7 @@ Be aware that if the remote peer is not
 Object setAttributeIfAbsent(Object key) : adds a new attribute with no 
value, if it does not already exist
 Object setAttributeIfAbsent(Object key, Object value) : adds a new 
attribute/value pair, if it does not already exist
 
+
 All those methods allows your application to store, remove, get or update 
the attributes stored into your session. Also note that some attributes are 
used internally by MINA : don't lightly modify those you didn't create !
 Filter chain¶
 Each session is associated with a chain of filters, which will be processed 
when an incoming request or an outgoing message is received or emitted. Those 
filters are specific for each session individually, even if most of the cases, 
we will use the very same chain of filters for all the existing sessions.

svn commit: r1761647 - /mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext

[elecharny]

Author: elecharny
Date: Tue Sep 20 22:02:55 2016
New Revision: 1761647

URL: http://svn.apache.org/viewvc?rev=1761647&view=rev
Log:
Fixed the formating, again

Modified:

mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext

Modified: 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext
URL: 
http://svn.apache.org/viewvc/mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext?rev=1761647&r1=1761646&r2=1761647&view=diff
==
--- 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext 
(original)
+++ 
mina/site/trunk/content/mina-project/userguide/ch4-session/ch4-session.mdtext 
Tue Sep 20 22:02:55 2016
@@ -199,18 +199,19 @@ and here is the factory interface we can
 
 There are many methods available to manipulate the session's attributes :
 
-* boolean containsAttribute(Object key) : tells if a given attribute is present
-* Object getAttribute(Object key) : gets the value for a given attribute
-* Object getAttribute(Object key, Object defaultValue) : gets the value for a 
given attribute, or a default value if absent
-* Set getAttributeKeys() : gets the set of all the stored attributes
-* Object removeAttribute(Object key) : remove a given attribute
-* boolean removeAttribute(Object key, Object value) : remove a given 
attribute/value pair
-* boolean replaceAttribute(Object key, Object oldValue, Object newValue) : 
replace a give attribute/value pair
-* Object setAttribute(Object key) : adds a new attribute with no value
-* Object setAttribute(Object key, Object value) : adds a new attribute/value 
pair
-* Object setAttributeIfAbsent(Object key) : adds a new attribute with no 
value, if it does not already exist
-* Object setAttributeIfAbsent(Object key, Object value) : adds a new 
attribute/value pair, if it does not already exist
-
+
+boolean containsAttribute(Object key) : tells if a given attribute is 
present
+Object getAttribute(Object key) : gets the value for a given attribute
+Object getAttribute(Object key, Object defaultValue) : gets the value for 
a given attribute, or a default value if absent
+Set\ getAttributeKeys() : gets the set of all the stored 
attributes
+Object removeAttribute(Object key) : remove a given attribute
+boolean removeAttribute(Object key, Object value) : remove a given 
attribute/value pair
+boolean replaceAttribute(Object key, Object oldValue, Object newValue) : 
replace a give attribute/value pair
+Object setAttribute(Object key) : adds a new attribute with no value
+Object setAttribute(Object key, Object value) : adds a new attribute/value 
pair
+Object setAttributeIfAbsent(Object key) : adds a new attribute with no 
value, if it does not already exist
+Object setAttributeIfAbsent(Object key, Object value) : adds a new 
attribute/value pair, if it does not already exist
+
 
 All those methods allows your application to store, remove, get or update the 
attributes stored into your session. Also note that some attributes are used 
internally by MINA : don't lightly modify those you didn't create !
 

svn commit: r997869 - in /websites/staging/mina/trunk/content: ./ mina-project/userguide/ch4-session/ch4-session.html

[buildbot]

Author: buildbot
Date: Tue Sep 20 22:04:17 2016
New Revision: 997869

Log:
Staging update by buildbot for mina

Modified:
websites/staging/mina/trunk/content/   (props changed)

websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html

Propchange: websites/staging/mina/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Tue Sep 20 22:04:17 2016
@@ -1 +1 @@
-1761647
+1761648

Modified: 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
==
--- 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
 (original)
+++ 
websites/staging/mina/trunk/content/mina-project/userguide/ch4-session/ch4-session.html
 Tue Sep 20 22:04:17 2016
@@ -324,7 +324,7 @@ Be aware that if the remote peer is not
 boolean containsAttribute(Object key) : tells if a given attribute is 
present
 Object getAttribute(Object key) : gets the value for a given attribute
 Object getAttribute(Object key, Object defaultValue) : gets the value for 
a given attribute, or a default value if absent
-Set\ getAttributeKeys() : gets the set of all the stored 
attributes
+Set