Java NIO Socket Framework / News: Recent posts

A new release alpha-1 has been made. It incorporates many bugfixes and improvements contributed by jkohen.

Additionally the binding between various parts has been reduced by introducing interfaces for the NioServerSocket and NioSocket classes. This change will also allow the implementation of datagram (UDP) servers.

The next step will be the introduction of some unit-tests.

The jniosocket has released an alpha-0 version of the upcoming jniosocket2 package. It is an early access release to show progress and where development is heading.

The following items were done:
* the class raining.jniosocket has been split
* samples for an http server and client have been added

ToDo:
* add logging
* add a DatagramSocket
* improve the examples
* add more examples
* add documentation... read more

The jniosocket project aims at providing a framework for easy building of highly scalable applications using the Java NIO sockets. With the addition of a new developer we hope to make some progress again.

Rahul Kumar, the project creator, has other priorities right now. He kindly accepted me, Thomas Klger, as additional developer and project administrator.

What are my goals?

* My main interest is rewriting the core class (raining.NioSocket) to build a solid foundation for extensions. Right now this class contains the polling loop, the server socket core and the client socket core. It will be split into three classes: net.sf.jniosocket.NioServer (polling, keep everything together), net.sf.jniosocket.NioServerSocket (listen and accept new connections) and net.sf.jnioSocket (handles the data streams).... read more

With release 1.2-3d, your applications can now use pipelining within a request (multiple GET requests in one connection). Connections are now persistent depending on the HTTP header passed.
This follows the rule for 1.0 and 1.1 as per RFC2616.

Current versions of 1.2pre have implementation of HTTP protocol using non-blocking sockets. You may now start writing highly scalable HTTP applications straight off using the new HTTP server. GET and HEAD are implemented, along with if-modified-since.

Some refactoring of code will take place prior to the final release of 1.2 (along with more HTTP updates).

I am currently working on a Server that has security and load conditioning features.
Incoming requests, domain names etc will have priorities.
The Server will exhibit "good behavior" at high loads.

Yes, the HTTP implementation is on hold.

I am currnelty working on implementing parts of the HTTP protocol (GET) using Java NIO.