W3C home > Mailing lists > Public > www-lib@w3.org > April to June 1999

New to libwww

From: amagrude <amagrude@kesmai.com>
Date: Sun, 4 Apr 1999 19:29:42 -0400
To: <www-lib@w3.org>
Message-ID: <000101be7ef3$052954a0$9ada98d0@kesmai.com>
Greetings,

I'm a development lead looking for an HTTP Client SDK and have spent a
significant amount of time looking at libwww.  Our requirements:

1. Resumable
2. Bandwidth throttling
3. HTTP 1.1 Client and Server (C/C++ only)

My question to y'all is:  am I in the right place?  Resumability looks
pretty straightforward and the HTTP 1.1 Client is a no-brainer.  I've
started to dig into the design to see how to do bandwidth throttling, but I
haven't found a good place to hang my hat yet.  Any suggestions would be
very helpful.

But it is the HTTP server piece that I am most concerned about.  I've dug up
a copy of MiniServ from libwww 4.1b5 and will start working with it.  For
this specific project I need to be able to push and files between HTTP
clients and Apache web servers and in between my various processes on
different hosts directly.  Given that I have a hard and fast requirement to
use only C/C++ (it's for a boxed computer game...) I at a loss as to how to
proceed.  When I discovered libwww I was excited because it is both a client
and a server in the same bundle of C code (code size is also an issue.)  But
further research has lead me to the fact that MiniServ is broken and maybe
the HTTP server piece in general.  My question is how and where is it broken
and what will it take to fix it?  Also, guidance on what exactly changed,
from an API perspective, between libwww 4.x and libwww 5.2.x to help with
the porting of MiniServ would be helpful.

Thanks for your time,

Andrew Magruder
Aries Producer
Kesmai Corporation
(804) 963-8598
Received on Sunday, 4 April 1999 19:32:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 April 2007 18:18:29 GMT