Implement nsBufferedOutputStream::WriteSegments and WriteFrom, and improve comments in other parts of necko
r=darin sr=bz
CVS: ----------------------------------------------------------------------
CVS: Enter Log. Lines beginning with `CVS:' are removed automatically
CVS:
CVS: Committing in .
CVS:
CVS: Modified Files:
CVS: base/public/nsISocketTransport.idl
CVS: base/public/nsITransport.idl base/src/nsBufferedStreams.cpp
CVS: base/src/nsFileStreams.cpp protocol/http/src/nsHttpChannel.cpp
CVS: ----------------------------------------------------------------------
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
memory leak of socket transports during pipelined request, add timeout
setters on socket transport, add a restriction on the number of keep-alive
connections.
can now be turned on (network.http.version=1.1); network.http.keep-alive can also
be used, however not recommended (1.1 pref will automatically enable keepa-alive).
r=warren,gagan
timeless%mozdev.org
darin%meer.net
scott%scott-macgregor.org
gerv%gerv.net
cbiesinger%web.de
darin%netscape.com
bbaetz%cs.mcgill.ca
dougt%netscape.com
disttsc%bart.nl
warren%netscape.com
jab%atdot.org
valeski%netscape.com
ruslan%netscape.com