post data to use this subclass. We'll now read in the post file asynchronously and write out the post
data asynchronously to the server. When necessary, we'll pause and resume the file request for the incoming
post data since that comes in faster than data goes out.
sr=bienvenu
r=ducarroz/varada
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
fix#56971 (correct spelling mistake: suppress not supress)
fix#60244 (subscribe retains only last server subscribe changes)
fix#60242 (subscribe typedown should select first match in list)
fix#39156 (fix how I determine the delimiter in subscribe.js)
fix#59231 (make insecure imap login work if password has a \ in it)
fix#53654 (subscribe downloaded bytes don't start at zero)
fix#39393 (stop button in subscribe)
fix#60506 (switching servers doesn't clear text area in subscribe)
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.
and useage in this class. Our underlying socket or file transport wasn't getting the right
load group. And we weren't passing the right load group out on on start / on stop requests.
r=rhp
we need to call Cancel() to remove the closed nsSocketTransport from the
list of active transports. if we don't, we quickly reach the max (50)
and pop, smtp, and nntp operation start failing.
also, upon NS_BINDING_ABORTED, do not pop up an alert. we get
this when we call Cancel() or if the user hits the stop button.
