Re: [cpp-netlib-devel] Some code already up in subversion

[Peter S. <si...@cr...>]

Hi guys, 

it took a while to remember my sf.net password, but in the end I
managed to commit. :-)

I have a question. In the boost-sandbox repository, everyone is
encouraged to add a top-level directory per project. An imaginary
foo library is organized in SVN as follows:

  foo / boost / foo.hpp
  foo / boost / foo / ...
  foo / libs  / foo / src  / ...
  foo / libs  / foo / doc  / ...
  foo / libs  / foo / test / ...

How would we like to handle that? What is the granularity we aim
for in this project? Let's say we come up with a very good class
for representing URIs. Do we try to make that URI library a
stand-alone component (that can be submitted to boost on its
own), or is URI something that's tightly integrated into
cpp-netlib?

Tight integration often leads to more efficient source code
because chances for re-use are higher. If things are integrated
too tightly, however, it is hard to use any one component of the
library without using everything else too. 

What are the components we anticipate to have in cpp-netlib? A
general purpose class for things that look like an "Internet
Message" is one of topics we need to address, but what else would
we like to see in Boost?

Best regards,
Peter