Revising nsIChannel to allow for overlapped i/o. This consists of three parts:
1. Factoring nsIChannel into a protocol specific part, the nsIChannel, and a socket specific, the nsITransport.
2. Derive the nsIChannel from a nsIRequest.
2. Changes the notification system from necko and the URILoader to pass the nsIRequest interface instead of nsIChannel interface.
This goal stems from wanting to be able to have active AsyncRead and AsyncWrite operations on nsSocketTransport.
This is desired because it would greatly simplify the task of maintaining persistent/reusable socket connections
for FTP, HTTP, and Imap (and potentially other protocols). The problem with the existing nsIChannel interface is
that it does not allow one to selectively suspend just one of the read or write operations while keeping the other active.
r=darin@netscape.comsr=rpotts@netscape.com
1. Factoring nsIChannel into a protocol specific part, the nsIChannel, and a socket specific, the nsITransport.
2. Derive the nsIChannel from a nsIRequest.
2. Changes the notification system from necko and the URILoader to pass the nsIRequest interface instead of nsIChannel interface.
This goal stems from wanting to be able to have active AsyncRead and AsyncWrite operations on nsSocketTransport.
This is desired because it would greatly simplify the task of maintaining persistent/reusable socket connections
for FTP, HTTP, and Imap (and potentially other protocols). The problem with the existing nsIChannel interface is
that it does not allow one to selectively suspend just one of the read or write operations while keeping the other active.
The full details of the change on written up in the netlib newsgroup.
r=darin@netscape.comsr=rpotts@netscape.com
as this code has been reconsolidated in the base class for
all to use. For everyone, if the mime type is unknown or octet,
then try to guess a content type by file extension in doContent.
Also, if we can't find a mime type, create a new one for all platforms
so we don't need to bring up the ucth dialog.
sr=sspitzer
we are already done with the download. Break apart
SaveTodisk and LaunchWithTempFile into to separate
methods. never try to really open or save to disk
until we are sure we've brought up the progress window.
Bug #61947 --> pass in the initial time when we started the download via getDownloadInfo so
the progress dialog can use this information.
sr=sspitzer
and force any Refresh urls back through the original window
context that initiated the helper app download. This solves
the problem where the user clicks on a link to download
content (either to disk or to a helper app) and that document
contains both a redirect for the actual content and a REFRESH
header which is used to point at a page the content provider
wants to see after the download is complete.
sr=rpotts, r=sspizter
some bad debugging code that was left in mimetypes.rdf for pdf back in beta2
for now, return an error. This will make use ignore this entry in the data source
when performing mime lookups....which is good 'cause that will have a side
effect of making application/pdf content work again.
r=sspitzer, a=alecf
after we show the helper app dialog. So progress and load information is
now retargeted to a stand alone window instead of re-using the underlying
browser / mail window...In order to do this, the external app handler needed to implement nsIURIContentListener.
sr=r=rpotts
UI up from the uriloader. This allows us to properly use a string bundle
for text in the dialog. this is prep work for the real fix for this bug.
r=law
jaggernaut%netscape.com
ducarroz%netscape.com
dougt%netscape.com
syd%netscape.com
sgehani%netscape.com
rpotts%netscape.com
darin%netscape.com
law%netscape.com
heikki%netscape.com
mscott%netscape.com
mkaply%us.ibm.com
timeless%mac.com
colin%theblakes.com
disttsc%bart.nl
warren%netscape.com
rayw%netscape.com
scc%mozilla.org
pchen%netscape.com
ccarlen%netscape.com