Re: Http_client infinite loop

Great.  I've checked out the code and have a few questions.

> - You can set multiple (e.g. cookie) headers
> - One can download large files to disk, or upload large files from disk

If I #set_response_body_storage `Memory, what happens if the response
is larger than 16 MB?

Presumably #response_body returns a mime_body_ro, and I can then use
#response_body#open_value_rd () to get an in_obj_channel, but is there
a way to pass this smoothly into PXP?  I'd prefer not to have to mess
with temporary files if that is avoidable.

> - No performance problems for large downloads

Never noticed any performance problems before, but this is still a
good thing!

> - Support for non-standard HTTP methods
> - Improved authentication framework
> - Improved compatibility to ocamlnet, esp. headers and bodies are
>   represented with the classes defined in Netmime.
> - Experimental support for connection caching

Connection caching is useful when you have multiple pipelines, right?
In all our programs we share a single pipeline (they are all single
threaded), so I'm assuming we would never need to use this feature.

Rich.

-- 
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com


-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar