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

11 Коммитов

Автор SHA1 Сообщение Дата
rpotts%netscape.com dc675a9675 bug #169583 (r=jst, sr=darin) URILoader should allow nsIContentHandler::DoContent() to fail... 2002-09-24 19:53:43 +00:00
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
rpotts%netscape.com f02e84c4bb bug #65777 (r=valeski, sr=mscott) - Window targeting fixes... 2001-05-14 02:16:27 +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
mscott%netscape.com 333edb2c69 Bug #30553 --> new windows with window targets were getting the target associated with the
chrome window instead of with the content window. And the window sizes were coming from the
	       hidden window instead of the parent window the url originated from.
r=travis
a=jevering
2000-03-09 08:17:40 +00:00
mscott%netscape.com 9a386e5c0a More prepation for docshell landing. Add a IsPreferred method to nsIURIContentListener and use the Ispreferred
method when the load type is user click to find the preferred registered window for handling the content

r=travis
2000-02-04 08:43:34 +00:00
dmose%mozilla.org 142ac52eaf updated xPL license boilerplate to v1.1, a=chofmann@netscape.com,r=endico@mozilla.org 1999-11-06 03:43:54 +00:00
mscott%netscape.com d07b92ce56 (not part of the seamonkey build!)
remove CanHandleConent. I don't think we need this. Also remove notion of getting a parent
content handler. This doesn't make sense anymore for how I'm defining a content handler.
Added progid prefix for content handler.
1999-11-05 22:52:35 +00:00
mscott%netscape.com 0069fa11da Moving URI dispatching code into its new home in mozilla\uriloader. I'll be removing
the existing files that I put in netwerk very soon.
1999-10-29 21:46:18 +00:00