Re: [boost] Boost.HTTP ?

From: Michael Dickey (mike_at_[hidden])
Date: 2007-12-10 15:28:42

Dean,

I think we could combine cpp-netlib's messaging classes with pion's  
HTTP parsing classes to establish a basis for HTTP processing and  
provide client-side support for HTTP/1.0 and 1.1.

There's two possible approaches to this that I see, one is to merge a  
"server" space into the Network library:

boost::net::basic_message<>
boost::net::http::request : public basic_message<>
boost::net::http::response : public basic_message<>
boost::net::server::tcp
boost::net::server::http : public tcp

Another would be to create an independent "server" library that uses  
the Network library classes:

boost::server::tcp
boost::server::http : public tcp

They both seem like sensible approaches to me.  In either case, I  
think that HTTP would be a good starting focus for both, to get a  
working foundation incorporated into boost.  We could always submit  
additional protocols independently for review as their implementations  
are finished.

What do you think?

Take care,
-Mike

On Dec 9, 2007, at 7:09 PM, Dean Michael Berris wrote:

>> I didn't mean to 'dis' the importance of the other protocols.  What  
>> I meant to
>> say is that if we try to bring an entire suite as one library, in  
>> one review,
>> it will a) take a long time, and b) be hard to manage.  So I'd  
>> rather see them
>> come as smaller contributions -- perhaps within a shared framework  
>> boost::net
>> or whatever.
>>
>
> Ah, yes. Now that makes sense to me.
>
> As to doing it by piece meal (HTTP first, then SMTP next perhaps)
> maybe we'd get more mileage. :)
>>>
>>> If Mike already has an HTTP client library we can retro-fit to work
>>> with the cpp-netlib basic_message<> implementation, then I think we
>>> don't have to re-invent the wheel as far as an HTTP client
>>> implementation goes -- and cpp-netlib 1.0 might just be around the
>>> corner once we document it properly and get it tested up to Boost
>>> standards.
>>
>> Looks to me like Mike is focused on the server side...so maybe  
>> there's not
>> much overlap anyway.
>>
>
> Too bad... That doesn't change though, cpp-netlib will be focused on
> the client side. Insights from the libpion implementation may help
> though, especially with HTTP 1.0/1.1 implementation details.
>
> -- 
> Dean Michael C. Berris
> Software Engineer, Friendster, Inc.
> [http://cplusplus-soup.blogspot.com/]
> [mikhailberis_at_[hidden]]
> [[phone]]
> [[phone]]
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
>