You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by ma...@apache.org on 2015/02/27 11:42:39 UTC
[2/5] activemq-6 git commit: Changes on configuring-transport:
Changes on configuring-transport:
I - Removing note about deprecated properties. Our configs are using it
II - useNIO property is irrelevant since we always use NIO now with the new netty
Project: http://git-wip-us.apache.org/repos/asf/activemq-6/repo
Commit: http://git-wip-us.apache.org/repos/asf/activemq-6/commit/6f9c4df9
Tree: http://git-wip-us.apache.org/repos/asf/activemq-6/tree/6f9c4df9
Diff: http://git-wip-us.apache.org/repos/asf/activemq-6/diff/6f9c4df9
Branch: refs/heads/master
Commit: 6f9c4df916d2666339e13357548563dbd7da397b
Parents: 90c2986
Author: Clebert Suconic <cl...@apache.org>
Authored: Thu Feb 26 22:23:06 2015 -0500
Committer: Clebert Suconic <cl...@apache.org>
Committed: Thu Feb 26 22:52:28 2015 -0500
----------------------------------------------------------------------
docs/user-manual/en/configuring-transports.md | 17 -----------------
1 file changed, 17 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/activemq-6/blob/6f9c4df9/docs/user-manual/en/configuring-transports.md
----------------------------------------------------------------------
diff --git a/docs/user-manual/en/configuring-transports.md b/docs/user-manual/en/configuring-transports.md
index 3267966..a275549 100644
--- a/docs/user-manual/en/configuring-transports.md
+++ b/docs/user-manual/en/configuring-transports.md
@@ -162,11 +162,6 @@ It is possible to limit which protocols are supported by using the
<connector name="netty">tcp://localhost:61617?protocols=CORE,AMQP</connector>
-
-> **Note**
->
-> The `protocol` parameter is now deprecated
-
## Configuring Netty TCP
Netty TCP is a simple unencrypted TCP sockets based transport. Netty TCP
@@ -196,18 +191,6 @@ Netty for simple TCP:
> The `host` and `port` parameters are only used in the core API, in
> XML configuration these are set in the URI host and port.
-- `useNio`. If this is `true` then Java non blocking NIO will be
- used. If set to `false` then old blocking Java IO will be used.
-
- If you require the server to handle many concurrent connections, we
- highly recommend that you use non blocking Java NIO. Java NIO does
- not maintain a thread per connection so can scale to many more
- concurrent connections than with old blocking IO. If you don't
- require the server to handle many concurrent connections, you might
- get slightly better performance by using old (blocking) IO. The
- default value for this property is `false` on the server side and
- `false` on the client side.
-
- `host`. This specifies the host name or IP address to connect to
(when configuring a connector) or to listen on (when configuring an
acceptor). The default value for this property is `localhost`. When