nsISocketTransportService functions can be called on
patch by Florian Quèze <florian@queze.net> r+sr=biesi
git-svn-id: svn://10.0.0.236/trunk@248131 18797224-902f-48f8-a5cc-f745e15eee43
mozilla. r=dougt,sr=rpotts. Help Windows NT, 2000, and XP dialup a RAS
connection when a network address is unreachable. (c/osmeredith)
the controlling pref is "network.autodial-helper.enabled".
git-svn-id: svn://10.0.0.236/trunk@124314 18797224-902f-48f8-a5cc-f745e15eee43
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
git-svn-id: svn://10.0.0.236/trunk@87587 18797224-902f-48f8-a5cc-f745e15eee43
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
git-svn-id: svn://10.0.0.236/trunk@86717 18797224-902f-48f8-a5cc-f745e15eee43
Bug #16103
Support for SOCKS proxies in HTTP, HTTPS, and FTP protocols.
Also includes the prefs configuration and UI bits.
git-svn-id: svn://10.0.0.236/trunk@73625 18797224-902f-48f8-a5cc-f745e15eee43
1) Passing the proxy hostname and port to the underlying socket
and changing all users that appeared in lxr.
2) (psm-glue) registering with the cache manager to allow local loopback so that
psm will work with a proxy.
3) (psm-glue) Storing proxy information in psmSocketInfo.
most reviewed by gagan@netscape.com.
git-svn-id: svn://10.0.0.236/trunk@70532 18797224-902f-48f8-a5cc-f745e15eee43
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
git-svn-id: svn://10.0.0.236/trunk@62838 18797224-902f-48f8-a5cc-f745e15eee43
