Re: [cpp-netlib-devel] Uring over here

[K. G. <kim...@gm...>]

Hi Dean,

On Sun, Oct 26, 2008 at 15:48, Dean Michael Berris
<mik...@gm...> wrote:
>
> So for instance I need a uri<http::url> to construct an http::request,
> then the parser of the uri<http::url> would take into consideration
> everything that needs to be included in a uri<http::url>.

You mean we should specialize the whole uri depending on a
protocol-specific tag? Or push the parsing code out to another
tag-dependent type (http::url, even)?

Coming from a more tired object-oriented background, I think all these
generic constructs are really counter-intuitive. I've learned to read
the stuff more or less (much thanks to guidance from this list), but I
still don't write it natively. It's like learning a new language --
reading/listening comes much faster than the ability to express
yourself confidently.

It'd be interesting to see a mapping chart from OO construct <->
generic construct, most of them have a counterpart on the other side.

- Kim