Add link to Vert.x 3 website

core_manual_clojure.html

@@ -782,6 +782,7 @@ <h4 id="getting-notified-of-reply-failures">Getting notified of reply failures</
   (fn [m]
     (eb/fail 123 "Not enough aardvarks")))
 
+
 (eb/send "test.address" "This is a message" 1000 
   (fn [err m]
     (if err

core_manual_java.html

@@ -855,6 +855,7 @@ <h1 id="json">JSON</h1><br/>
 
 eb.send("some-address", obj);
 
+
 // ....
 // And in a handler somewhere:
 
@@ -1850,7 +1851,8 @@ <h3 id="serving-files-directly-from-disk">Serving files directly from disk</h3><
 <p><strong>If you're going to write web servers using Vert.x be careful that users cannot exploit the path to access files outside the directory from which you want to serve them.</strong></p>
 <h3 id="pumping-responses">Pumping Responses</h3><br/>
 <p>Since the HTTP Response implements <code>WriteStream</code> you can pump to it from any <code>ReadStream</code>, e.g. an <code>AsyncFile</code>, <code>NetSocket</code>, <code>WebSocket</code> or <code>HttpServerRequest</code>.</p>
-<p>Here's an example which echoes HttpRequest headers and body back in the HttpResponse. It uses a pump for the body, so it will work even if the HTTP request body is much larger than can fit in memory at any one time:</p>
+<p>Here's an example which echoes HttpRequest headers and body back in the HttpResponse.
+ It uses a pump for the body, so it will work even if the HTTP request body is much larger than can fit in memory at any one time:</p>
 <pre class="prettyprint">HttpServer server = vertx.createHttpServer();
 
 server.requestHandler(new Handler&lt;HttpServerRequest&gt;() {
@@ -2381,7 +2383,8 @@ <h2 id="sockjs-client">SockJS client</h2><br/>
 <p>As you can see the API is very similar to the WebSockets API.</p>
 <h1 id="sockjs-eventbus-bridge">SockJS - EventBus Bridge</h1><br/>
 <h2 id="setting-up-the-bridge">Setting up the Bridge</h2><br/>
-<p>By connecting up SockJS and the Vert.x event bus we create a distributed event bus which not only spans multiple Vert.x instances on the server side, but can also include client side JavaScript running in browsers.</p>
+<p>By connecting up SockJS and the Vert.x event bus we create a distributed event bus which not only spans multiple Vert.x
+ instances on the server side, but can also include client side JavaScript running in browsers.</p>
 <p>We can therefore create a huge distributed bus encompassing many browsers and servers. The browsers don't have to be connected to the same server as long as the servers are connected.</p>
 <p>On the server side we have already discussed the event bus API.</p>
 <p>We also provide a client side JavaScript library called <code>vertxbus.js</code> which provides the same event bus API, but on the client side.</p>

core_manual_js.html

@@ -2076,6 +2076,7 @@ <h2 id="securing-the-bridge">Securing the Bridge</h2><br/>
   ]
   );
 
+
 httpServer.listen(8080);
 </pre>
 <p>To let all messages through you can specify two JSON array with a single empty JSON object which will match all messages.</p>

core_manual_python.html

@@ -2084,6 +2084,7 @@ <h2 id="securing-the-bridge">Securing the Bridge</h2><br/>
     }
   ], [{}])
 
+
 server.listen(8080)
 </pre>
 <p>To let all messages through you can specify two arrays with a single empty JSON object which will match all messages.</p>
@@ -2334,6 +2335,7 @@ <h3 id="random-access-writes">Random access writes</h3><br/>
                     print 'Written ok'  
             async_file.write(buff, buff.length() * i, write_handler)
 
+
 fs.open('some-file.dat', handler=handler)
 </pre>
 <h3 id="random-access-reads">Random access reads</h3><br/>

core_manual_ruby.html

@@ -2016,6 +2016,7 @@ <h2 id="securing-the-bridge">Securing the Bridge</h2><br/>
     }
   ])
 
+
 server.listen(8080)
 </pre>
 <p>To let all messages through you can specify two arrays with a single empty JSON object which will match all messages.</p>

core_manual_scala.html

@@ -844,6 +844,7 @@ <h1 id="json">JSON</h1><br/>
 val obj = Json.obj("foo" -&gt; "wibble", "age" -&gt; 1000)                                     
 eb.send("some-address", obj)
 
+
 // ....
 // And in a handler somewhere:
 

docs_md/core_manual_java.md

@@ -2010,7 +2010,8 @@ There's also a version of `sendFile` which takes the name of a file to serve if
 
 Since the HTTP Response implements `WriteStream` you can pump to it from any `ReadStream`, e.g. an `AsyncFile`, `NetSocket`, `WebSocket` or `HttpServerRequest`.
 
-Here's an example which echoes HttpRequest headers and body back in the HttpResponse. It uses a pump for the body, so it will work even if the HTTP request body is much larger than can fit in memory at any one time:
+Here's an example which echoes HttpRequest headers and body back in the HttpResponse.
+ It uses a pump for the body, so it will work even if the HTTP request body is much larger than can fit in memory at any one time:
 
     HttpServer server = vertx.createHttpServer();
 
@@ -2724,7 +2725,8 @@ As you can see the API is very similar to the WebSockets API.
 
 ## Setting up the Bridge
 
-By connecting up SockJS and the Vert.x event bus we create a distributed event bus which not only spans multiple Vert.x instances on the server side, but can also include client side JavaScript running in browsers.
+By connecting up SockJS and the Vert.x event bus we create a distributed event bus which not only spans multiple Vert.x
+ instances on the server side, but can also include client side JavaScript running in browsers.
 
 We can therefore create a huge distributed bus encompassing many browsers and servers. The browsers don't have to be connected to the same server as long as the servers are connected.
 

index.html

@@ -78,6 +78,25 @@
 
 <br />
 
+
+<div class="row">
+
+  <div class="span12">
+    <div class="highlight">
+      <h3 class="highlight_title">What's new in Vert.x 3?</h3>
+
+      <br/>
+
+      <p><a href="http://vert-x3.github.io/">Take a sneaky-peak</a> at the exciting new stuff in the soon-to-be released Vert.x 3.0!</p>
+      <p>Please note! Vert.x 3 is still a work-in-progress</p>
+
+    </div>
+  </div>
+</div>
+
+<br/>
+
+
 <div class="row">
 
   <div class="span3">

index_templ.html

@@ -21,6 +21,25 @@
 
 <br />
 
+
+<div class="row">
+
+  <div class="span12">
+    <div class="highlight">
+      <h3 class="highlight_title">What's new in Vert.x 3?</h3>
+
+      <br/>
+
+      <p><a href="http://vert-x3.github.io/">Take a sneaky-peak</a> at the exciting new stuff in the soon-to-be released Vert.x 3.0!</p>
+      <p>Please note! Vert.x 3 is still a work-in-progress</p>
+
+    </div>
+  </div>
+</div>
+
+<br/>
+
+
 <div class="row">
 
   <div class="span3">

vertx1x_docs/core_manual_java.html

@@ -684,6 +684,7 @@ <h1 id="json">JSON</h1><br/>
 
 eb.send("some-address", obj);
 
+
 // ....
 // And in a handler somewhere:
 

vertx1x_docs/core_manual_js.html

@@ -1939,6 +1939,7 @@ <h2 id="securing-the-bridge">Securing the Bridge</h2><br/>
   ]
   );
 
+
 server.listen(8080);
 </pre>
 <p>To let all messages through you can specify two arrays with a single empty JSON object which will match all messages.</p>

vertx1x_docs/core_manual_python.html

@@ -1977,6 +1977,7 @@ <h2 id="securing-the-bridge">Securing the Bridge</h2><br/>
     }
   ], [{}])
 
+
 server.listen(8080)
 </pre>
 <p>To let all messages through you can specify two arrays with a single empty JSON object which will match all messages.</p>
@@ -2227,6 +2228,7 @@ <h3 id="random-access-writes">Random access writes</h3><br/>
                     print 'Written ok'  
             async_file.write(buff, buff.length() * i, write_handler)
 
+
 FileSystem.open('some-file.dat', handler=handler)
 </pre>
 <h3 id="random-access-reads">Random access reads</h3><br/>

vertx1x_docs/core_manual_ruby.html

@@ -1903,6 +1903,7 @@ <h2 id="securing-the-bridge">Securing the Bridge</h2><br/>
     }
   ])
 
+
 server.listen(8080)
 </pre>
 <p>To let all messages through you can specify two arrays with a single empty JSON object which will match all messages.</p>