Release 0.3 available in Sourceforge

This post is to announce the release of version 0.3 of the C++ Network Library (with apologies for failing to announce the release of 0.2 on this blog ;).

Updates include:

* Improved documentation;
* Additional constructors for http::client with arguments for following redirects and clearing the resolver cache;
* Updated unit testing.

Release 0.1 Now Available in Sourceforge

This is just a quick note to let the world know that the C++ Network Library now has an 0.1 release available from the Sourceforge project site. This 0.1 release includes:

• Messaging Framework


• HTTP 1.0 Client with GET, PUT, DELETE, POST, and HEAD suppport


• Initial Unit Tests

This is an early Alpha release which does not have enough documentation. The 0.2 release is scheduled Monday (September 1st, 2008) which should include HTML documentation and more changes.

Please join the mailing list and try out the software and be part of the development of the library!

Open Thread: Your Pet Peeves

I'm writing this post to ask potential users of the C++ Network Library what their worst experiences are with existing networking libraries, and what you'd want to see (or not see) in a new network library. I personally have my motivation for working on a new network library in C++ because of past (and present) experiences. These personal motivations are already pretty much documented in the rationale for the library (and the architecture document) but I'd like to know what people think should be the other goals of the C++ Network Library.

Currently, I'm focusing my time implementing an HTTP Client with the most features useful to me (and the new generation of web-aware software) that I'm having tunnel-vision as to what I'm supposed to be doing and how I'm supposed to be doing it. Knowing from the audience what they would want to see next would be a nice refresher to let the team know what sort of thing we should be working on in the project.

So what are your pet peeves (and/or worst experiences) with existing networking libraries that you want addressed in a new network library? Let us know!

HTTP Client: Supports GET, HEAD, POST, PUT, and DELETE

After a long time coming, the C++ Network Library now supports the standard HTTP commands that modern clients need. In the branch http_integration, I've been able to implement a synchronous HTTP Client implementation that supports the major HTTP commands.

What's left to be done is to write more unit tests and actually use it in real-life applications. Fast approaching is an asynchronous client implementation, and eventually a 1.0 alpha.

We need help in the following areas:

- Testing
- Debugging
- Documentation

If you want to be part of the project, please don't hesitate to join us in the C++ Network Library Developers mailing list.

HTTP 1.0 Implementation now in trunk!

Okay, this will be quick.

Yesterday I was able to come up with a really crude yet functional HTTP 1.0 client. This is already available in the subversion repository, and ready for more unit tests to make sure that we can cover more cases before shipping. Help would be definitely appreciated in terms of writing unit tests and refactoring/improving the URI parser and the client implementation.

More information to come in the next few days as I continue developing the HTTP implementation.

So if you have time to spare and brain cycles to donate, we'd definitely appreciate the help!

Software requirements

I've put up the beginnings of software requirements specification on the C++ Network wiki. I hope this could spark a bit of debate and we can make some more progress when its decided exactly what networking features we'd like to add to C++.

Project Co-ordination

The first announcement I can make is that I have installed myself (in a benevolent 3rd world dictator kind of way) as release manager/project co-ordinator. This will free Dean to continue outlining his vision with the architecture documentation and I will hope to be able to encourage some people to contribute ideas, time or other resources to this project.

If you want to contribute, take a look at our mailing list and we'll be interested to hear what your thoughts are.