Netty 4.0.51 and 4.1.15. final versions released

New updates for a NIO client server framework available now
29 August 2017   1900

New bugfix releases for Netty 4.0.x and 4.1.x series available now. 

What is Netty? 

Netty is a NIO client server framework which enables quick and easy development of network applications such as protocol servers and clients. It greatly simplifies and streamlines network programming such as TCP and UDP socket server.

'Quick and easy' doesn't mean that a resulting application will suffer from a maintainability or a performance issue. Netty has been designed carefully with the experiences earned from the implementation of a lot of protocols such as FTP, SMTP, HTTP, and various binary and text-based legacy protocols. As a result, Netty has succeeded to find a way to achieve ease of development, performance, stability, and flexibility without a compromise.

Netty architecture
Netty architecture

Main features:

  • Design
    • Unified API for various transport types - blocking and non-blocking socket
    • Based on a flexible and extensible event model which allows clear separation of concerns
    • Highly customizable thread model - single thread, one or more thread pools such as SEDA
    • True connectionless datagram socket support (since 3.1)
  • Ease of use
    • Well-documented Javadoc, user guide and examples
    • No additional dependencies, JDK 5 (Netty 3.x) or 6 (Netty 4.x) is enough
  • Performance
    • Better throughput, lower latency
    • Less resource consumption
    • Minimized unnecessary memory copy
  • Security
    • Complete SSL/TLS and StartTLS support

What's new in updates?

These releases contains bug-fixes, performance enhancements and features.

The most important changes for 4.0.51.Final and 4.1.15.Final are:

  • Support JDK9-native ALPN 
  • More bullet-proof way of detecting if ipv6 is supported or not when using the native transport 
  • DelegatingSslContext should also be able to configure the SslHandler 
  • Netty 4.1.14.Final fails to load on android
  • Include JNIEXPORT on exported symbols 
  • Unify KQueue and Epoll wait timeout approach 
  • Make NativeLibraryLoader check java.library.path first 
  • Use the ByteBufAllocator when copy a ReadOnlyByteBufferBuf and so also be able to release it without the GC when the Cleaner is present 
  • Ensure netty builds with java9 (build 9+181) 
  • Make configurable the initial and max size of InternalThreadLocal.stringBuilder 
  • Fix endless loop in ByteBufUtil#writeAscii 
  • Correctly support SO_TIMEOUT for OioDatagramChannel 
  • Ensure we null out the previous set InetAddress on 
  • Correctly handle connect/disconnect in EpollDatagramChannel
  • Shutting down the outbound side of the channel should not accept future writes

The most important changes for 4.1.15.Final only are:

  • Decouple DnsCache and DnsCacheEntry 
  • KQueue detect peer close without EVFILT_READ
  • Support the little endian floats and doubles by ByteBuf 
  • We should prefer heap buffers when using the OIO transport to reduce memory copies 
  • First call channelReadComplete(...) before flush(...) for better performance 
  • HTTP/2 Child Channel and FrameCodec Feature Parity  

 Learn more at official website.

TIOBE Index June 2019 to be Rolled Out

Java is still on the top, but experts noted fast growth of Python search queries, and they believe it can reach 1st place in 3-4 years
13 June 2019   319

June 2019 TIOBE Index has been released. Analysts noted a sharp increase in the proportion of searches for Python.

This month Python has reached again an all time high in TIOBE index of 8.5%. If Python can keep this pace, it will probably replace C and Java in 3 to 4 years time, thus becoming the most popular programming language of the world. The main reason for this is that software engineering is booming. It attracts lots of newcomers to the field. Java's way of programming is too verbose for beginners. In order to fully understand and run a simple program such as "hello world" in Java you need to have knowledge of classes, static methods and packages. In C this is a bit easier, but then you will be hit in the face with explicit memory management. In Python this is just a one-liner. 


Experts attributed the growing popularity of Python to the fact that now many have hit the development of software. And newcomers prefer Python - succinct and concise. According to analysts, Java for beginners is too verbose, and C sooner or later will force to understand the intricacies of memory management.