8 Commits

Author SHA1 Message Date
dougt%netscape.com
4b7b8b12ca Fixes bug 83401. r=gagan, darin, sr=vidur, a=blizzard. Add port blacklisting to necko
git-svn-id: svn://10.0.0.236/trunk@96470 18797224-902f-48f8-a5cc-f745e15eee43
2001-06-06 00:10:09 +00:00
pavlov%netscape.com
185c0f4ec5 fixing build bustage
git-svn-id: svn://10.0.0.236/trunk@91856 18797224-902f-48f8-a5cc-f745e15eee43
2001-04-10 07:10:30 +00:00
darin%netscape.com
9d03c579d0 Necko API changes, bug 74221. r=valeski, sr=rpotts.
git-svn-id: svn://10.0.0.236/trunk@91842 18797224-902f-48f8-a5cc-f745e15eee43
2001-04-10 06:01:08 +00:00
dougt%netscape.com
175245e2de Relanding Necko Changes.
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.com
sr=rpotts@netscape.com


git-svn-id: svn://10.0.0.236/trunk@87587 18797224-902f-48f8-a5cc-f745e15eee43
2001-02-21 20:38:08 +00:00
disttsc%bart.nl
03f69c5003 Back out dougt's channel changes
git-svn-id: svn://10.0.0.236/trunk@86793 18797224-902f-48f8-a5cc-f745e15eee43
2001-02-12 03:14:23 +00:00
dougt%netscape.com
7af79c83df 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.

The full details of the change on written up in the netlib newsgroup.

r=darin@netscape.com
sr=rpotts@netscape.com


git-svn-id: svn://10.0.0.236/trunk@86717 18797224-902f-48f8-a5cc-f745e15eee43
2001-02-10 00:16:26 +00:00
mscott%netscape.com
bc268e0986 Bug #63193 --> the external protocol handler should only return a url or a new channel if we really do
have an external app that can handle the url. otherwise return NS_ERROR_UNKNOWN_PROTOCOL so we'll throw up an alert
dialog later on.
sr=sspizter


git-svn-id: svn://10.0.0.236/trunk@86497 18797224-902f-48f8-a5cc-f745e15eee43
2001-02-07 05:24:27 +00:00
mscott%netscape.com
a2ec5045b5 Bug #63193 --> add these two new files for a default protocol handler which will kick urls out to the OS
sr=rpotts


git-svn-id: svn://10.0.0.236/trunk@86419 18797224-902f-48f8-a5cc-f745e15eee43
2001-02-07 01:21:58 +00:00