Re: [cpp-netlib-devel] URI processing (Was Re: Work Left)

[Dean M. B. <mik...@gm...>]

Hi Kim,

On Fri, Oct 10, 2008 at 8:55 PM, Kim Gräsman <kim...@gm...> wrote:
> Hi guys,
>
> On Thu, Oct 9, 2008 at 20:39, Glyn Matthews <gly...@gm...> wrote:
>>
>> Well it's not really part of the HTTP integration.  And it's not much better
>> doing all development in a single branch than doing it all in trunk.  What I
>> think is best is to develop different tasks in different branches, while
>> testing against trunk.  Ideally, branches should correspond to a
>> task/subproject on the sf site too.
>
> I created a branch succinctly called 'uri', on
> https://cpp-netlib.svn.sourceforge.net/svnroot/cpp-netlib/branches/uri
>
> I've committed the first fumbling parts there, in
> /boost/network/uri.hpp and /libs/network/test/uri_test.hpp.
>

Quick question: where did you branch from? trunk or http_integration?

> At least it's a start, not sure where to go from there...
>
> I didn't parameterize the string type mainly because the default tag
> is under network/protocol/http, and the URI goes one level up in the
> hierarchy, but I suppose I could introduce a temporary tag to wrap the
> string typedef.
>

That raises a good issue though: should we have a single place to have
the tags hierarchy depicted?

I'm thinking:

namespace network {
  struct tags {
    struct http {
      struct message {
        struct tag { };
      };
      // ...
    };
    struct message {
      struct tag { };
    };
    // ...
  };
}

That way we can build traits on top of this hierarchy under a
different namespace 'traits':

namespace network { namespace traits {
  template <class Tag> string;
  template <class Tag> buffer;
  template <class Tag> ostringstream;
  template <class Tag> char_;
  // ...
} }

And specialize them as necessary as well?

-- 
Dean Michael C. Berris
Software Engineer, Friendster, Inc.