[cpp-netlib-devel] library goals and roadmap

[Jose <jm...@gm...>]

Hi,

I would like to get a basic agreement on the goals and roadmap, so that we
can choose where to contribute and avoid duplicating effort. Pls send me
your comments so that
we can get a more concrete document

General library goals
===============

- Performance (do not pay for what you don't use)
I think this is a goal for many C++ libraries and it is specially important
for  a c++ network library

- Reusability of protocol classes
Already discussed. Very important to the protocol designer

- Protocol conformance
I think this is key for the success of the library. There are many protocol
implementations out there and what really hampers them is that they provide
a partial implementation, which looks like a proof of concept but not a
complete one. So, whatever protocols are choosen (client or/and server
side), they should be fully implemented otherwise users will fork their own
implementations (which is fine but contradicts the value of a library)

Below is a basic list of protocols (which should be in order of priority).
It has already been stated in the mailing list that the library goal is to
provide reusable protocol development components and a few protocol
implementations. Applications like web server or email server could be
provided but it is not a goal to provide competitive application
implementations.

Protocol Roadmap
==============

* HTTP 1.0 client
    - URI parser
    - request object
    - reply parser
* SMTP client
    - pls send the list of key features
* HTTP 1.1 client
    - cookies
    - gzip
    - multipart mime
    - easy interface to async DNS
* HTTPS
* ESMTP client
* HTTP 1.0 server
* HTTP 1.1 server
* ESMTP server

Example Applications
================

Web server, email server, ...


Pls send your comments

regards
jose