Thread: [cpp-netlib-devel] cpp-netlib 0.8 Target Deliverables

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hi Guys!

To those new on the mailing list, welcome -- and to those who have
been lurking or wanting to contribute to the effort but find it really
hard this lack of direction, then here's your chance.

As most of you already know I'm working on cpp-netlib full-time now.
No I still don't have work, so I'm making use of my time in between
finding work to work on cpp-netlib and move it closer to something
worth submitting into Boost by December this year (yes, 2010). So I'm
sending my Google Task list for cpp-netlib to the list so everyone
knows what to expect from 0.8.

I'll also be creating issues and Wiki pages on the official project
repository at http://github.com/cpp-netlib/cpp-netlib. From now on,
only experimental "work-in progress" stuff goes onto my repository
(and those pull requests from others who want to join the effort
should still be sent to my repository) while the "stable" and
"milestone" achievements get pushed to the official repo as soon as
they are done.

If you have any questions or would like clarifications, please feel
free to send them in through the mailing list. :D

--8<-----------

Release 0.8 -- Target is 1st Week of November
	Integrate XMPP Implementation from Glyn
	Refactor HTTP Client Constructor to use Boost.Parameter
	Callback thread pool
		Configurable number of threads
		Taken in as constructor parameter to asynchronous HTTP clients
	Implement Callback-based HTTP Client API
	Streaming HTTP Client API
		Implement a basic_response<> which has a boost::asio::iostream bound
to a socket for the body
		Implement a basic_request<> which has a stream for the body
		client.get(request, callback) where callback is of signature
void(basic_response<Tag>)
		client.put(request) where body(request) models an InputStream
	Server Handler Facade
		CRTP to provide default implementation for PUT, POST, GET, and HEAD handlers
		Simplify parameter and header parsing
		Simplify parameter validation and requirement specification
	Web Service Framework
		Dynamic Handler Registration
		Path Routing (regex)
		Request Normalization
	HTTP Server Handler Work Pool
		Implement a work pool to handle requests
		Implement a basic_request<> that has a stream for the body
		Implement a http_connection<> that exposes asynchronous routines for output
			Expose a set_headers function that takes a range of
pair<string,string> elements and writes that out through the HTTP
connection
			Expose a write function that takes a range as input and
asynchronously sends the data through the HTTP connection
			Expose a close function that closes the connection from the server's end
	Implement a basic_server<> that requires the handler type to override
the function call operator and take a basic_request<> and an
http_connection<> as parameters

--8<-----------------

As always, thanks again for the support and I look forward to your
contributions to release 0.8.

-- 
Dean Michael Berris
deanberris.com