Salut,
we will soon get serious competition on the HTTP side :-)
A+
-- Jeanfrancois
-------- Original Message --------
Subject: Netty 3.1.0.ALPHA1 released - HTTP and convenient service shutdown
Date: Thu, 27 Nov 2008 04:40:59 +0900
From: Trustin Lee <tlee_at_redhat.com>
Reply-To: Netty -Dev List <netty-dev_at_lists.jboss.org>
Organization: JBoss, a division of Red Hat
To: Netty Announcements <netty-announce_at_lists.jboss.org>
CC: Netty Users <netty-users_at_lists.jboss.org>, Netty Developers
<netty-dev_at_lists.jboss.org>
Hi community,
Netty 3.1.0.ALPHA1, the beginning of the another major feature release
iteration has been released. 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
HTTP Codec
==========
Thanks to Andy Taylor's contribution, this first alpha release ships
with a preliminary implementation of HTTP codec. It's a low level codec
that enables the development of highly customized HTTP clients and
servers. Please take a look at the HTTP client/server example:
*
http://tinyurl.com/5w3fpb
You will find a great degree of freedom and little restriction, which
means it's completely up to you to conform to the standard or not. If
there's enough demand, Netty could provide more high-level standard
compliant HTTP component which is similar to what Apache HttpComponents
provides.
I'd like appreciate Andy's effort again to make this possible sooner
than I originally expected. Please let us know if anything is missing
or any improvement in the API is required.
More Convenient Service Shutdown
================================
Many users have been asking how to shut down a service correctly so that
there's no remaining threads. There was an explicitly documented
procedure to shut down a service, but it was somewhat complicated than
it is supposed to be.
In this release, ChannelFactoryResource interface has been added to
simplify the service shut down procedure. All client examples have been
updated to demonstrate this feature. For instance, the FactorialClient
example is much more elegant than before - no more System.exit()!
*
http://tinyurl.com/5d7xoa
It still requires you to close all open channels managed by the
ChannelFactory, but it will be dealt with in the next release.
Channel.getCloseFuture()
========================
It is now possible to wait until a channel is closed more conveniently.
You will always be notified with a channelClosed event whan a channel is
closed as Netty does in 3.0, but Channel.getCloseFuture() will give you
more choice on it. It's especially useful when you write a client
application and want to wait until a channel is closed in background:
Channel c = ...;
c.getCloseFuture().awaitUninterruptibly();
Upcoming Releases
=================
All features added in this release will be reviewed continuously
following up your feed back. A couple more alpha versions will be
released with more new features and improvements. Please feel free to
browse the road map and let us know what you think about it:
*
http://tinyurl.com/5vpxux
Please also note that we are always open to your suggestion and
contribution on any feature which is not listed in the road map yet. :)
Miscellaneous
=============
For the detailed changelog, please visit here:
*
http://tinyurl.com/5ztogv
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
--
Trustin Lee, Principal Software Engineer, JBoss, a division of Red Hat
--
what we call human nature in actuality is human habit
--
http://gleamynode.net/
_______________________________________________
netty-dev mailing list
netty-dev_at_lists.jboss.org
https://lists.jboss.org/mailman/listinfo/netty-dev