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

12 Коммитов

Автор SHA1 Сообщение Дата
cbiesinger%web.de 3c212719bf bug 239604. make uriloader more doxygen friendly, and remove unused "command"
parameter from nsIContentHandler::handleContent, and change the type of
aWindowContext to nsIInterfaceRequestor.
r=bzbarsky sr=darin
2004-04-16 21:06:07 +00:00
rpotts%netscape.com 0e293491d8 bug #169583 (r=jst, sr=darin) URILoader should allow nsIContentHandler::DoContent() to fail... 2002-09-24 19:53:43 +00:00
gerv%gerv.net f385eb981a 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 f3e719c2c1 bug #65777 (r=valeski, sr=mscott) - Window targeting fixes... 2001-05-14 02:16:27 +00:00
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
mscott%netscape.com 1bb75e24b4 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 d468643d79 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 8535dda53e 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 c5c728a09b (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 6d59c5d592 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