Sunday 21 November 2010
The C++ Network Library v0.8 Out Now!
The C++ Network Library team is proud to announce the availability of version 0.8 of the library after one whole week of getting feedback on the Beta version. The library is being maintained by Dean Michael Berris the project founder (and author of this blog) and is being supported by the C++ Network Library Developers through the cpp-netlib developers mailing list. You can get the latest version of the library from the Github repository downloads page. You can also find out more about cpp-netlib's 0.8 release from the online home of its documentation at http://cpp-netlib.github.com/0.8/.
Sunday 12 July 2009
C++ Network Library and Trac
After a period of low activity, some problems are apparent. Over the last few months there has been some activity on the mailing list from people who have expressed a will to get involved with development but for one reason or another have not been able to get started or make any progress. I believe a lot of this has to do the fact that we're not maintaining an up-to-date schedule or roadmap, and its difficult for new contributors to find out where or how they should start.
For this reason I have decided to add Trac to the sourceforge site. The URL is:
http://sourceforge.net/apps/trac/cpp-netlib/
This has a number of advantages over what we currently have:
* It allows us to set up milestones and components, to give a better overview of the current project progress
* There's an integrated and intuitive source browser
* There's a ticket tracker which allows tickets to be assigned to milestones and components
While these are in some form available through sourceforge's project page, they're not cohesive in the same way as Trac is.
If people are happy with this, then as a first step I'd urge you to start adding tickets and bug reports. For those who want to do some development then contact the mailing list.
I hope this is a step that allows us to better track progress and gives an incentive for new members to contribute.
For this reason I have decided to add Trac to the sourceforge site. The URL is:
http://sourceforge.net/apps/trac/cpp-netlib/
This has a number of advantages over what we currently have:
* It allows us to set up milestones and components, to give a better overview of the current project progress
* There's an integrated and intuitive source browser
* There's a ticket tracker which allows tickets to be assigned to milestones and components
While these are in some form available through sourceforge's project page, they're not cohesive in the same way as Trac is.
If people are happy with this, then as a first step I'd urge you to start adding tickets and bug reports. For those who want to do some development then contact the mailing list.
I hope this is a step that allows us to better track progress and gives an incentive for new members to contribute.
Monday 20 October 2008
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.
Updates include:
* Improved documentation;
* Additional constructors for http::client with arguments for following redirects and clearing the resolver cache;
* Updated unit testing.
Tuesday 26 August 2008
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:
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!
- 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!
Thursday 14 August 2008
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!
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!
Monday 11 August 2008
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.
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.
Tuesday 9 October 2007
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!
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!
Subscribe to:
Posts (Atom)