Re: [cpp-netlib-devel] authentication and project files

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

Hi Stjepan!

On 5/22/07, Stjepan Rajko <st...@as...> wrote:
> Hi all,
>
> I just took a quick glance at the code, and am wondering how
> authentication will be addressed in the library (since that's my main
> interest :-))
>

The short answer would be, that it should be handled on a per-protocol
basis. We can definitely use the boost::network::message to contain
the necessary information to be dealt with by the protocol
implementation.

So if there's a protocol like SMTP where there's a need for a username
and password, my suggestion would be that there should be a
"boost::network::smtp::credentials" object which encapsulates that
information.

> For HTTP and SMTP this might not be an issue, but looking ahead what
> are the thoughts on this?  Will the user just put together a message
> which contains the necessary information in the headers / body, and
> send it off through an appropriate authentication object, or will
> there be a separate layer that takes care of the authentication?  A
> related issue is how lasting connections will be handled.
>

As for lasting connections, Boost.Asio already provides stuff that can
be re-used and simply re-worked and packaged so that they're used in a
more generic way (instead of having to implement the same keepalive
implementation on all applications that need this functionality or
something similar).

> Also, I've been working on the template-based generator for
> boost/sandbox projects - once we've checked that it actually complies
> with Boost guidelines, I can generate some IDE projects (for msvc and
> xcode) and fill-in-the-blanks docs / doc-build-files for this project.
>  Any problems with me adding that when it's ready?
>

I don't know what you mean, but when we do have the code to build in
different platforms (I'm guessing we won't because I intend to keep
this library "header only") then things like that would help. For now
though, I'd rather stick with Boost.Build + Boost.Test for the
testing, maybe some Quickbook + doxygen for the documentation, among
other things.

We'll see if we can use the stuff you're working on too -- if it can
help us write better docs quickly, then I guess we should definitely
go for it. :)

Thanks much! :)

-- 
Dean Michael C. Berris
http://cplusplus-soup.blogspot.com/
mikhailberis AT gmail DOT com
+63 928 7291459