Skip to content

Commit e742df2

Browse files
committed
Remove event-bus write handler documentation.
1 parent 3622078 commit e742df2

File tree

2 files changed

+0
-24
lines changed

2 files changed

+0
-24
lines changed

vertx-core/src/main/asciidoc/http.adoc

Lines changed: 0 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -2219,19 +2219,6 @@ The {@link io.vertx.core.http.WebSocket} instance is also a {@link io.vertx.core
22192219
When using a WebSocket as a write stream or a read stream it can only be used with WebSockets connections that are
22202220
used with binary frames that are no split over multiple frames.
22212221

2222-
==== Event bus handlers
2223-
2224-
Every WebSocket can register two handlers on the event bus, and when any data are received in these handlers,
2225-
it writes the data to itself. Those are local subscriptions, not reachable from other clustered nodes.
2226-
2227-
This enables you to write data to a WebSocket which is potentially in a completely different verticle sending data
2228-
to the address of that handler.
2229-
2230-
This feature is disabled by default, however you can enable it using {@link io.vertx.core.http.HttpServerOptions#setRegisterWebSocketWriteHandlers} or {@link io.vertx.core.http.WebSocketConnectOptions#setRegisterWriteHandlers}.
2231-
2232-
The addresses of the handlers are given by {@link io.vertx.core.http.WebSocket#binaryHandlerID()} and
2233-
{@link io.vertx.core.http.WebSocket#textHandlerID()}.
2234-
22352222
=== Using a proxy for HTTP/HTTPS connections
22362223

22372224
The {@link io.vertx.core.http.HttpClient} supports accessing HTTP/HTTPS URLs via an HTTP proxy (e.g. Squid), a _SOCKS4a_, or a _SOCKS5_ proxy.

vertx-core/src/main/asciidoc/net.adoc

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -131,17 +131,6 @@ You can set an {@link io.vertx.core.net.NetServer#exceptionHandler(io.vertx.core
131131
exceptions that happens before the connection is passed to the {@link io.vertx.core.net.NetServer#connectHandler(io.vertx.core.Handler)}
132132
, e.g during the TLS handshake.
133133

134-
=== Event bus write handler
135-
136-
Every socket can register a handler on the event bus, and when any buffers are received in this handler,
137-
it writes them to itself. Those are local subscriptions, not reachable from other clustered nodes.
138-
139-
This enables you to write data to a socket which is potentially in a completely different verticle by sending the buffer to the address of that handler.
140-
141-
This feature is disabled by default, however you can enable it using {@link io.vertx.core.net.NetServerOptions#setRegisterWriteHandler} or {@link io.vertx.core.net.NetClientOptions#setRegisterWriteHandler}.
142-
143-
The address of the handler is given by {@link io.vertx.core.net.NetSocket#writeHandlerID()}.
144-
145134
=== Local and remote addresses
146135

147136
The local address of a {@link io.vertx.core.net.NetSocket} can be retrieved using {@link io.vertx.core.net.NetSocket#localAddress()}.

0 commit comments

Comments
 (0)