cpp-netlib-devel

[cpp-netlib-devel] PUT, POST, and DELETE support

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

Hi Guys,

As promised, I've further refactored the code of the HTTP Client and
implemented POST, PUT, and DELETE.

The API now looks like the following:

client object
  - .put(request) : crafts a put request from the request object,
without modification
  - .put(request, body) : crafts a copy of the request and adds a
body, default content-type is 'x-application/octet-stream',
content-length is body.size()
  - .put(request, content_type, body) : crafts a copy of the request
and adds a body, content-type is content_type, content-length is
body.size()
  - .post(request) : crafts a post request from the request object,
without modification
  - .post(request, body) : crafts a copy of the request and adds a
body, default content-type is 'x-application/octet-stream',
content-length is body.size()
  - .post(request, content_type, body) : crafts a copy of the request
and adds a body, content-type is content_type, content-length is
body.size()
  - .delete_(request) : crafts a delete request from the request object

I have just checked in the code without unit tests -- maybe someone
who knows how to deal with the Python Server (CGI perhaps) and do
POST, PUT, and DELETE handling should take over the testing of this
code?

Any takers? :D

Have a good day everyone! :)

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

Re: [cpp-netlib-devel] PUT, POST, and DELETE support

[Divye K. <div...@gm...>]

Hi Dean,
   It is possible for a POST request to send multiple body entities with
multiple content types using multipart transmission (RFC 2388)
Should we support this feature? In order to do that, we will need to analyse
the body of the message to determine suitable boundaries.

I have just checked in the code without unit tests -- maybe someone
who knows how to deal with the Python Server (CGI perhaps) and do
POST, PUT, and DELETE handling should take over the testing of this
code?


There is no direct support for PUT and DELETE on the Python server
currently. I'll see how that can be implemented.

Divye

-- 
An idealist is one who, on noticing that a rose smells better than a
cabbage, concludes that it will also make better soup.
H. L. Mencken (1880 - 1956)
My official web site: http://people.iitr.ernet.in/shp/061305/
Webmaster: http://www.drkapoorsclinic.com
Blog: http://divyekapoor.blogspot.com

Re: [cpp-netlib-devel] PUT, POST, and DELETE support

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

Hi Divye,

On Mon, Aug 11, 2008 at 9:39 PM, Divye Kapoor <div...@gm...> wrote:
> Hi Dean,
>    It is possible for a POST request to send multiple body entities with
> multiple content types using multipart transmission (RFC 2388)
> Should we support this feature? In order to do that, we will need to analyse
> the body of the message to determine suitable boundaries.
>

That should be pretty easy to do. I'm thinking of adding the following
to support this:

  -.post(request, range<pair<string,string> >)

Where the range contains a mapping between content-type and content.
>From within, we recreate the actual request with the correct headers
and the body that contains the correct format/delimiter. Or even,
using Boost.Fusion:

  post(request, sequence)

Where sequence is a Fusion sequence of STL pairs.

> I have just checked in the code without unit tests -- maybe someone
> who knows how to deal with the Python Server (CGI perhaps) and do
> POST, PUT, and DELETE handling should take over the testing of this
> code?
>
> There is no direct support for PUT and DELETE on the Python server
> currently. I'll see how that can be implemented.
>

Oh. It might be something worth looking into. Thanks in advance.

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