зеркало из https://github.com/mozilla/pjs.git
84 строки
3.4 KiB
Plaintext
84 строки
3.4 KiB
Plaintext
/* -*- Mode: C++; tab-width: 2; indent-tabs-mode: nil; c-basic-offset: 4 -*-
|
|
*
|
|
* The contents of this file are subject to the Netscape Public
|
|
* License Version 1.1 (the "License"); you may not use this file
|
|
* except in compliance with the License. You may obtain a copy of
|
|
* the License at http://www.mozilla.org/NPL/
|
|
*
|
|
* Software distributed under the License is distributed on an "AS
|
|
* IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
|
|
* implied. See the License for the specific language governing
|
|
* rights and limitations under the License.
|
|
*
|
|
* The Original Code is mozilla.org code.
|
|
*
|
|
* The Initial Developer of the Original Code is Netscape
|
|
* Communications Corporation. Portions created by Netscape are
|
|
* Copyright (C) 1999 Netscape Communications Corporation. All
|
|
* Rights Reserved.
|
|
*
|
|
* Contributor(s):
|
|
*/
|
|
|
|
/* nsIURIContentListener is an interface used by classes which
|
|
want to know (and have a chance to handle) a particular content type.
|
|
Typical useage scenarios will include running applications which register
|
|
a nsIURIContentListener for each of its content windows with the uri dispatcher
|
|
service.
|
|
*/
|
|
|
|
#include "nsISupports.idl"
|
|
#include "nsIURILoader.idl"
|
|
|
|
interface nsIProtocolHandler;
|
|
interface nsIChannel;
|
|
interface nsIStreamListener;
|
|
interface nsIURI;
|
|
|
|
[scriptable, uuid(94928AB3-8B63-11d3-989D-001083010E9B)]
|
|
interface nsIURIContentListener : nsISupports
|
|
{
|
|
/* Give the content listener first crack at forcing us to use
|
|
a specific content handler. Content listener's do not need to
|
|
support this method if they want the uri dispatcher to find the
|
|
default protocol handler from the registry.
|
|
|
|
aURI --> the uri we need a protocol handler for
|
|
aProtocolHandler --> the protocol handler you want the uri loader
|
|
to use. You can pass back null if you want the uri loader to look
|
|
up an appropriate protocol handler
|
|
*/
|
|
void getProtocolHandler(in nsIURI aURI, out nsIProtocolHandler aProtocolHandler);
|
|
|
|
/* The URIDispatcher will give the content listener a shot at handling
|
|
the content before it tries other means. If the content listener
|
|
wants to handle the content then it should return a stream listener
|
|
the data should be pushed into.
|
|
aContentType --> the content type we need to handle
|
|
aCommand --> verb for the action (this comes from layout???)
|
|
aWindowTarget --> name of the target window if any
|
|
aStreamListener --> the content viewer the content should be displayed in
|
|
You should return null for this out parameter if you do
|
|
not want to handle this content type.
|
|
aAbortProcess --> If you want to handle the content yourself and you don't
|
|
want the dispatcher to do anything else, return TRUE for
|
|
this parameter.
|
|
*/
|
|
|
|
void doContent(in string aContentType,
|
|
in nsURILoadCommand aCommand,
|
|
in string aWindowTarget,
|
|
in nsIChannel aOpenedChannel,
|
|
out nsIStreamListener aContentHandler,
|
|
out boolean aAbortProcess);
|
|
|
|
/* returns true if we can handle the content and false if we can't.
|
|
aDesiredContentType --> yes, we can accept aContentType but we would
|
|
like it converted to aDesiredContentType. This argument can be null if
|
|
you want the content directly as aContentType */
|
|
boolean canHandleContent(in string aContentType,
|
|
in nsURILoadCommand aCommand,
|
|
in string aWindowTarget,
|
|
out string aDesiredContentType);
|
|
};
|