On 29/04/07, Sam Lawrance <[EMAIL PROTECTED]> wrote:
> 2. Depending on the server's side, this particular program could
> get into a
> deadlock since it relays on the server having large enough buffers
> to send
> files and receive requests before the client finishes sending all
> the file
> nam
On 28/04/07, Sam Lawrance <[EMAIL PROTECTED]> wrote:
Yes, single file at a time would suck over a network. HTTP/1.1 is a
good suggestion, but you need to use pipelining. Demonstrated use
(at least in my mind :-) is FreeBSD's portsnap, which is becoming the
preferred method to transfer hundreds
On 21/04/07, Robert Collins <[EMAIL PROTECTED]> wrote:
Last I checked RC2616 does not defnied multipart/related semantics for
HTTP.
So here is a though I had after reading your response - how about sending
back one MIME content contain multi-parts inside it?
As far as I follow the following l
On Sat, 2007-04-21 at 22:43 +1000, Amos Shapira wrote:
> Hello,
>
> Does anyone have a pointer for a sample of code which sends multiple files
> as a single HTTP response using MIME multipart/related?
>
> All the code or explanations I found so far are talking about either
> creating MIME e-mail
Hello,
Does anyone have a pointer for a sample of code which sends multiple files
as a single HTTP response using MIME multipart/related?
All the code or explanations I found so far are talking about either
creating MIME e-mail messages or parsing multipart responses (or even upload
of multiple
