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
use the status of the last request processed in loading the document to determine
success or failure. That's incorrect. Instead, test to see if the load group is being
canceled. If it is, use that as the status for the entire document. Otherwise, ignore
the status for the last request and instead use the status for the main document
(the default load channel).
sr=rpotts, r=sspitzer
+ Added dummy function to all users of nsIWebProgressListener
+ Added new security event sink.
+ Hooked up new event sink to docloader and friends.
+ Fixed memory leaks and crashes in nsSecureBrowserImpl.
+ Added AlertPrompt to nsIPrompt Interface.
+ Enabling xpcom test on unix.
Fixes bug 46872. r=valeski/rpotts
because we aren't told if the main document url is getting redirected or if a part (like an
image) is getting redirected. This caused the urlbar to get incorrectly updated.
r=sspitzer
through the web progress interfaces. In order to implement progress, the doc loader now implements
nsIProgressEventSink and receives events directly from the channels.
I was signaling the stop notification via a OnchildStatus in this scenario. We should always signal the start
and stop of documents as a status change even if a child is originating the change.
nsIWebProgressListener.
Right now, the only methods that are hooked up are signaling when the doc loader is busy loading a document and
when it is done loading a document.
remove protocol scheme check before using the uri loader. this
means that all urls will run through the uriloader regardless of
type when it gets turned on.
webshell:
doContent and canHandleContent now take a nsURILoaderCommand
modify the handle link click event method to pass in
in the nsIURILoader::viewUserClick command to the uri loader
r=travis
dougt%netscape.com
disttsc%bart.nl
valeski%netscape.com
rpotts%netscape.com
mscott%netscape.com
warren%netscape.com
locka%iol.ie
jdunn%netscape.com
pavlov%netscape.com
tbogard%aol.net
ftang%netscape.com
norris%netscape.com
morse%netscape.com
danm%netscape.com