Граф коммитов

17 Коммитов

Автор SHA1 Сообщение Дата
dougt%netscape.com eab041f43f 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 76fbedadc5 Back out dougt's channel changes 2001-02-12 03:14:23 +00:00
dougt%netscape.com 69415757ab 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
darin%netscape.com 6bfaf3912c Bug 62566. nsIChannel::AsyncWrite interface revision and related cleanup.
r=dougt@netcape.com, sr=mscott@netscape.com.
2001-01-23 22:10:34 +00:00
warren%netscape.com 64a99efec0 Bug 46864 - Embedding needs a name attribute on nsIRequest. 2000-08-21 08:23:54 +00:00
warren%netscape.com 7ac7233df8 Factored string bundles out of necko. Fixes bug 42107 - need to fix string bundle init workaround. Also bug 40506 - nsIWebProgressListener needs status text. Status messages now work in mozilla and viewer with internationalized and parameterized text! Added temporary error architecture until bug 13423 can be fixed. Extended nsIStringBundleService to provide method to format status message. r=valeski,jband,tao. verified=mstoltz 2000-07-25 05:45:56 +00:00
valeski%netscape.com c9ce86137e 42767. AsyncOpen (dead code) removal. 2000-06-16 14:39:19 +00:00
warren%netscape.com 870a7d208a Fix to make jar protocol not copy local files. Starting to get chrome to work with jars. Bug #18433 2000-06-02 23:39:45 +00:00
dougt%netscape.com 0da3936bb1 correcting invalid port number. They should be -1, not zero. 2000-05-20 00:19:24 +00:00
dougt%netscape.com 4ea1d81354 Fix for 31164, possibly 35658, and prep work for 31174.
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.
2000-05-19 22:56:12 +00:00
warren%netscape.com 942ccefd74 Added nsIZipReaderCache. Removed nsIZipReader::ParseManifest. Got jar: protocol going for downloaded jars and input streams. Added assertions that Cancel is called with a failure code. 2000-04-12 07:58:24 +00:00
warren%netscape.com d60b12b153 Necko API changes: primarily nsIChannel, changing initialization parameters to accessors. Got javascript: evaluation to happen at the right time (when AsyncRead is called) as well as on the right thread. 2000-03-29 03:58:50 +00:00
dougt%netscape.com 612badb3a9 Adding GetSecurityInfo to the nsIChannel. bug 29646. r=warren. 2000-03-17 22:06:32 +00:00
valeski%netscape.com 6ea2e883bf r=rhp. datetime protocol wasn't initializing properly which would cause a datetime url without a host to spin 2000-01-11 22:16:19 +00:00
rpotts%netscape.com 3e79b2aec1 Made contentType a read/write attribute of nsIChannel 2000-01-08 06:26:04 +00:00
valeski%netscape.com 0baa09fd90 NOT IN BUILD. updating datetime protocol to add/remove itself from the load group 1999-12-21 19:40:05 +00:00
valeski%netscape.com 54bce75ff9 NOT IN BUILD. Adding date time protocol handler files 1999-12-20 21:48:15 +00:00