Commit Graph

8 Commits

Author SHA1 Message Date
gerv%gerv.net
4e12e44b2f Relicensing Round 1, Take 2. Most C-like NPL files -> NPL/GPL/LGPL. Bug 98089. 2001-09-28 20:14:13 +00:00
darin%netscape.com
199c44a737 Http branch landing: changes to netwerk/ (bug 76866) r=gagan,sr=dougt,a=chofmann 2001-05-11 21:04:09 +00:00
darin%netscape.com
dac21e34cd Completes transistion from ULONG_MAX to PRUint32(-1) which was intended to
fix frizilla redness.  pinkerton checked in the necessary ones; this is
just for completeness.  r=gagan,sdagley,sfraser,pinkerton
2001-03-23 03:32:26 +00:00
darin%netscape.com
01253d7390 Fixes bug 66516. Topperf regression from 1/23. r=dougt, sr=mscott 2001-03-08 07:53:40 +00:00
bryner%uiuc.edu
8b80c7c363 Bug 70595 - making nsIPrompt accessible to PSM. r=darin, sr=mscott. 2001-03-06 05:10:33 +00:00
dougt%netscape.com
128f95aa9b 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
2001-02-21 20:38:08 +00:00
disttsc%bart.nl
3d2d80d536 Back out dougt's channel changes 2001-02-12 03:14:23 +00:00
dougt%netscape.com
1b9ca82439 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
2001-02-10 00:16:26 +00:00