asynchronous downloads

2002-10-03 Thread Andrew G. Hammond 

How do I send a file asynchronously?

The classic example is download sites.  You click on the file you want and
it generates a thankyou page for your browser and also sends the file.

So what's the correct way to do this?

Re: asynchronous downloads

2002-10-03 Thread dom 

 How do I send a file asynchronously?
 
 The classic example is download sites.  You click on the file you want and
 it generates a thankyou page for your browser and also sends the file.
 
 So what's the correct way to do this?
 

  Use a refresh META tag on the thank-you page, that points to the
requested file. Look at any download page at SourceForge to see how it
is done.

  Alternatively, you can return a multipart/mixed MIME message with
both documents as the result of the HTTP request.

-- 
Dominique QUATRAVAUX   Ingénieur développeur senior
01 44 42 00 27 IDEALX

Re: asynchronous downloads

2002-10-03 Thread Kevin Berggren 

I think many sites use the meta refresh html tag.  i.e.

htmlhead
...
META HTTP-EQUIV=Refresh CONTENT=2;URL=file_i_want_to_download.gz
...

Netscape has a complete reference on this at 
http://developer.netscape.com/docs/manuals/htmlguid/tags3.htm#1697602

You could probably also set a refresh header.

I hope this helps.

-kb

Andrew G. Hammond wrote:
 How do I send a file asynchronously?
 
 The classic example is download sites.  You click on the file you want and
 it generates a thankyou page for your browser and also sends the file.
 
 So what's the correct way to do this?

[OT] Re: asynchronous downloads

2002-10-03 Thread Issac Goldstand 


- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 03, 2002 5:09 PM
Subject: Re: asynchronous downloads


  How do I send a file asynchronously?
 
  The classic example is download sites.  You click on the file you want
and
  it generates a thankyou page for your browser and also sends the file.
 
  So what's the correct way to do this?
 

   Use a refresh META tag on the thank-you page, that points to the
 requested file. Look at any download page at SourceForge to see how it
 is done.

   Alternatively, you can return a multipart/mixed MIME message with
 both documents as the result of the HTTP request.


Actually, that is not defined for HTTP.  Although people commonly
interchange the Content-Type field defined by HTTP, and that defined by
MIME, the two are not interchangable.  The closest that HTTP comes to
working with multipart fields is the multipart/form-data Content-Type
defined in RFC 2388 (http://www.ietf.org/rfc/rfc2388.txt)  As it happens, I
noticed this a couple of years ago, and am currently planning an I-D which
will implement multipart/related HTTP responses.  If anyone at all is
interested in this, please don't hesitate to contact me about it - BUT,
let's keep that off-list, please :-)

  Issac