Netty 3.1.0.BETA2 released - A New Chapter in the User Guide and Dead Lock Auto-detection

[Stefan Ackermann]

Hi Trustin,

Here is a small patch for the documentation. Nothing big.
Also this sentence seems broken in architecture chapter: "The lack of
portability between transports becomes a problem when you need to support
more transports not rewriting the network layer of the application."

Other than that its good.

Cheers,
Stefan


On Sat, Apr 18, 2009 at 7:13 PM, Virat Gohil <virat4lug at gmail.com> wrote:

> Hi Trustin,
>
> Congratulations to Netty for reaching another milestone :). R 3.1 is
> coming together really well. You have been doing excellent stuff and
> at an exceptional pace. Its a pleasure working with Netty.
>
> Cheers!
>
> Virat
>
>
> On Sat, Apr 18, 2009 at 9:35 PM, Trustin Lee <tlee at redhat.com> wrote:
> > Hi folks,
> >
> > Netty 3.1.0.BETA2, the second beta release of 3.1 branch, has been
> released.
> >
> > The Netty project is an effort to provide an asynchronous,
> > event-driven network application framework and tools for rapid
> > development of maintainable, high-performance, high-scalability
> > protocol servers and clients.
> >
> > In other words, Netty is a NIO client server framework that enables
> > quick and easy development of network applications such as protocol
> > servers and clients. It simplifies and streamlines network programming
> > such as TCP and UDP socket servers.
> >
> > Please visit our web site to download it:
> >
> >   * http://www.jboss.org/netty/
> >
> > As always, your feed back is more than appreciated.  Please visit the
> > discussion forum and leave some comments and questions:
> >
> >   * http://www.jboss.org/netty/community.html
> >
> > A New Chapter in the User Guide
> > ===============================
> > If you were following us at Twitter ( http://twitter.com/netty_project
> > ), you might already have noticed that we updated the user guide to
> > reflect the feed back from the community.  Please check it out; it
> > worths a read! - http://tinyurl.com/b2snx4
> >
> > Dead Lock Auto-detection
> > ========================
> > It is a common mistake for a Netty beginner to call
> > ChannelFuture.await*() method when a ChannelHandler is running in an
> > I/O worker thread.  The ChannelFuture implementation now throws an
> > IllegalStateException if a user called ChannelFuture.await*() from an
> > I/O worker thread.  Just in case you didn't know about this, please
> > read the updated Javadoc of ChannelFuture: http://tinyurl.com/dyooey
> >
> > SSL Bug Fixes
> > =============
> > A couple issues related with SslHandler were found by community
> > members, and they were all fixed thanks to the detailed bug report
> > from them.  I'd like to say thank you again to Virat Gohil, Bryan
> > Wagner, and Huican Ping, in no particular order.
> >
> > Upcoming Releases
> > =================
> > If there's no noticeable bugs and I have done enough documentation and
> > testing, the next release will be 3.1.0.CR1 (Candidate Release).
> > Otherwise, it will be 3.1.0.BETA3.  Please keep us updated with any
> > bugs, design issues, API usability feed back, and questions.
> >
> > Miscellaneous
> > =============
> > For the full changelog, please visit here:
> >
> >   * http://tinyurl.com/cnz2wm
> >
> > Again, as always, your feed back is more than appreciated.  Please
> > visit the discussion forum and feel free to leave some comments and
> > questions:
> >
> >   * http://www.jboss.org/netty/community.html
> >
> > Cheers,
> >
> > — Trustin Lee, http://gleamynode.net/
> >
> > _______________________________________________
> > netty-users mailing list
> > netty-users at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/netty-users
> >
>
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-users/attachments/20090418/ebee5641/attachment.html 
-------------- next part --------------
Index: src/docbook/module/architecture.xml
===================================================================
--- src/docbook/module/architecture.xml	(revision 1220)
+++ src/docbook/module/architecture.xml	(working copy)
@@ -78,7 +78,7 @@
     </para>
     <para>
       This mismatch makes porting a network application from one transport to
-      the other.  The lack of portability between transports becomes a problem
+      the other tedious. The lack of portability between transports becomes a problem
       when you need to support more transports not rewriting the network layer
       of the application.  Logically, many protocols can run on more than one
       transport such as TCP/IP, UDP/IP, SCTP, and serial port communication.
Index: src/docbook/module/buffer.xml
===================================================================
--- src/docbook/module/buffer.xml	(revision 1220)
+++ src/docbook/module/buffer.xml	(working copy)
@@ -67,8 +67,8 @@
       By contrast, &ChannelBuffer; does not have such caveats because it is
       fully extensible and has a built-in composite buffer type.
     </para>
-    <programlisting>&ChannelBuffer;<co id="example.buffer2.co1"/> message = &Channels;.wrappedBuffer(header, body);
-&ChannelBuffer;<co id="example.buffer2.co2"/> messageWithFooter = &Channels;.wrappedBuffer(message, footer);
+    <programlisting>&ChannelBuffer;<co id="example.buffer2.co1"/> message = &ChannelBuffers;.wrappedBuffer(header, body);
+&ChannelBuffer;<co id="example.buffer2.co2"/> messageWithFooter = &ChannelBuffers;.wrappedBuffer(message, footer);
 messageWithFooter.getUnsignedInt(
     messageWithFooter.readableBytes() - footer.readableBytes() - 1<co id="example.buffer2.co3"/>);</programlisting>
     <calloutlist>
@@ -107,10 +107,10 @@
       <classname>StringBuffer</classname> to expand the capacity of its
       internal buffer on demand.  Netty allows you to do the same via
       a <firstterm>dynamic</firstterm> buffer which is created by the
-      &Channels;<literal>.</literal><methodname>dynamicBuffer()</methodname>
+      &ChannelBuffers;<literal>.</literal><methodname>dynamicBuffer()</methodname>
       method.
     </para>
-    <programlisting>&ChannelBuffer;<co id="example.buffer3.co1"/> dynamicBuffer = &Channels;.dynamicBuffer(4);
+    <programlisting>&ChannelBuffer;<co id="example.buffer3.co1"/> dynamicBuffer = &ChannelBuffers;.dynamicBuffer(4);
 dynamicBuffer.writeByte('1');<co id="example.buffer3.co2"/>
 dynamicBuffer.writeByte('2');
 dynamicBuffer.writeByte('3');