US 6,460,058 B2Grant
Object-oriented framework for hyperlink navigation
Issue Date:2002-10-01
•8 Claims
•13 Drawing Sheets
Abstract
An object-oriented framework comprises system services, objects, and integration interfaces which unify retrieval and browsing of data among multiple different application programs, document formats, and local and remote data storage sites. The framework provides a hyperlink object which encapsulates general hyperlink navigation functions. The hyperlink object has a moniker which references a hyperlink's target, and a location string which designates a location in the target. The hyperlink object uses the moniker to retrieve the target as an object in the framework, and causes the object to display a view of the target at the location. The framework also provides a browse context object which maintains a navigation stack of navigated hyperlink targets, and allows passing of window and navigation tool bar position information to a frame in which the target is displayed to effect the appearance of window reuse when navigating between frames. The framework also includes a cache and table of running objects to speed return navigation to recently navigated targets.
Metadata
Assignee
- Microsoft Corporation
Inventors
- Srinivasa R. Koppolu
- Victor Stone
- Benjamin W. Slivka
- David S. Ebbo
- Satoshi Nakajima
- Clarence Glasse
- Richard J. Wolf
Application Information
Application Number:US 08/761,709
Filing Date:1996-12-06
Priority Date:1996-12-06
Art Unit:7
Classifications
IPC:
G06F 1500
Field of Search:
707501707513707102707103707104395156345738
Patent Drawings (13 sheets)
Description
Field of the Invention
[0002] This invention relates generally to systems and methods for browsing or navigating to and retrieving data on a computer, and more particularly relates to browsing data of different varieties and from different sources in a unified manner.
Background and Summary of the Invention
[0003] Previous techniques and mechanisms for navigating to and retrieving data in a computer system have had significant drawbacks which pose obstacles to providing unified tools for browsing data seamlessly and transparently from all sources (including local storage, local networks, and remote networks).
[0004] An example of a previous system for navigating to and retrieving data is the user interface of the Microsoft Windows® 95 operating system. This interface displays “folder views” which show the contents (e.g., files and sub-directories) of file system directories (also referred to as “folders”) on the computer's local storage (e.g., hard or floppy disk drive) or a connected local area network (“LAN”). The folder views show files in a folder using one of four display modes: large icon, small icon, list, and details. A user navigates to a document by opening successive folder views beginning with a “my computer” or “network neighborhood” folder view (which are a top or “root” folder in the file systems of the local storage and LAN, respectively), and then selecting a particular file represented in the folder view. In response, the operating system loads an application program associated with the file, and causes the application program to “open” the file. This results in the application program displaying the contents of the file in a window (i.e., rectangular display area on the computer monitor's screen).
[0005] These folder views provide a unified and consistent way of navigating to data stored as files in a computer's local storage or on a connected LAN. But, navigation using the folder views also is limited in many respects. The folder views do not permit equivalent navigation to data stored remotely, such as on the Internet or on-line services. The folder views also do not retain any navigation “state” information, which would allow retracing or returning to data which has been previously navigated. The only state remaining after navigation with a folder view is that the folder view in which a file is selected remains open as a separate window in the Windows® 95 user interface.
[0006] Another example of a previous navigation system is an Internet browser, such as the Netscape Navigator or the Microsoft® Internet Explorer. Internet browsers have generally supported navigation using hyperlinks between hypertext documents residing on the World-Wide Web. The Internet is a global network of cooperatively interconnected computer networks, consisting of millions of individual computers. A portion of the Internet referred to as the “World-Wide Web” consists of computers, also referred to as “sites,” which make multi-media documents in hyper-text mark-up language (HTML) format generally available for downloading or retrieval by individuals having a computer with Internet access.
[0007] The HTML documents can contain “hyperlinks,” which are references (e.g., in the form of a uniform resource locator or URL) to another HTML document on the World-Wide Web or to another part of the same document. Generally, the hyperlinks are displayed as underlined or otherwise highlighted text, or a graphic within the document which the user can activate by “clicking” using a mouse or other input device. When a hyperlink is activated, the Internet browser navigates to the document that the hyperlink references by retrieving and displaying the referenced document in place of a currently displayed document.
[0008] Internet browsers typically maintain navigation state information in the form of a navigation log or “history” of previously navigated documents. The Browser uses the history to provide “go back” and “go forward” controls with which the user can backtrack and retrace a path between previously navigated documents. Some browsers also provide a “favorites” or “bookmark” feature with which the user creates a list of user-selected HTML documents for future reference. The user can later return to the document by selecting it from the favorites list.
[0009] However, previous Internet browsers also have failed to provide unified browsing of different varieties of data from different sources. The typical previous Internet browser is an HTML document viewer application which can display an HTML document within an application window, and supports hyperlink navigation which replaces one HTML document with another in the same application window. (An application window is the display area under control of the application in a graphical user interface (GUI) of an operating system.) This typical browser cannot display other varieties of documents (e.g., a Microsoft® Word application document), and doesn't allow hyperlink navigation to such documents. In short, such typical browsers allow hyperlink navigation between only HTML documents and only within a single application window.
[0010] One browser, the Microsoft® Internet Explorer, version 2.0 (hereafter the IE 2.0 browser), supports hyperlink navigation to a non-HTML document in a separate application window. More specifically, if the destination document of a hyperlink is a non-HTML document, the IE 2.0 browser determines the application associated with the document (such as by looking up the document's file name extension in the Windows® operating system registry) and causes that application to be launched with the document opened in a separate application window (e.g., through a shell execute command of the Windows® operating system). For example, if the user activates a hyperlink to a Microsoft® Word document on the Internet (at e.g., “http://www.microsoft.com/intdev/ie2spec.doc”), the IE 2.0 browser causes the Microsoft® Word application to be loaded (if the application is installed on that computer) and to open the document in its window.
[0011] However, the IE 2.0 browser still fails to provide unified navigation. When a hyperlink is navigated to a separate application window of a non-HTML document with the IE 2.0 browser, hyperlink navigation is effectively “dead-ended.” To continue hyperlink navigation, the user must switch windows back to the IE 2.0 browser window. There also is no “go back” hyperlink control or command available to return from the non-HTML document in the separate application window back to the HTML document in the IE 2.0 browser window. Instead, the user must switch windows using operating system mechanisms, such as the “control +escape” or “control +tab” hot key combinations of the Microsoft Windows® operating system. Thus, hyperlink navigation in the IE 2.0 browser is still limited to a single application window since the separate application window of a non-HTML document cannot fully participate in hyperlink navigation.
[0012] Further, the hyperlink navigation of the IE 2.0 browser to a non-HTML document in a separate application window does not have the same effect as typical hyperlink navigation. In typical hyperlink navigation, navigating a hyperlink replaces the document which contains the hyperlink with another document that is the destination or target of the hyperlink. Conversely, when navigating to a non-HTML document, the IE 2.0 browser causes an application associated with the non-HTML document to be launched in a separate window. This separate application window can be nearly anywhere on the computer screen, and may be either windowed or full screen (typical application windows retain the size and position settings from when they were last open). Meanwhile, the HTML document that contains the hyperlink remains open in the IE 2.0 browser window. As a result, unless both the IE 2.0 browser window and the separate application window both happen to be full-sized, the document displayed in the separate application window does not replace the HTML document in the IE 2.0 browser window and may not overlap any part of the IE 2.0 browser window.
[0013] A unified browsing environment based on the hyperlink navigation browsing model is provided in the present invention by an object-oriented framework and system having objects, programming interfaces, object integration interfaces, and methods for supporting unified navigation among different varieties of documents, data, and application programs. The invention overcomes the limitation in previous Internet browsers of navigating within a single application window, and provides seamless navigation between multiple document types and applications.
[0014] According to one aspect of the invention, the object-oriented framework includes a hyperlink object which encapsulates information needed to navigate a hyperlink, and the action of navigating the hyperlink. In the illustrated embodiment of the invention, the hyperlink object is a system-defined object which supports an integration interface that allows other programs to use the hyperlink object for navigating the hyperlink. The hyperlink object contains a moniker to a target of the hyperlink, a character string designating a destination location within the target, a descriptive name for the hyperlink (“friendly name”), and other parameters.
[0015] According to another aspect of the invention, the object-oriented framework further includes a browse context object and integration interfaces for a hyperlink container object, a hyperlink target object and a hyperlink frame object. The browse context object maintains a history of navigated hyperlinks, and other context information for hyperlink navigation including window size and position. The integration interfaces of these objects allow multiple different applications to interact with the browse context so as to participate fully in hyperlink navigation. With the browse context and integration interfaces, the applications can provide “go back” and “go forward” controls which retrace prior hyperlink navigation activity between the applications. The applications also can use the browse context to position and size the destination application window of the hyperlink so as to create the appearance of replacing the originating application window of the hyperlink. The system thereby allows seamless hyperlink navigation between different document types and applications.
[0016] According to a further aspect of the invention, the system also includes a set of programming interfaces which allow applications to participate in unified browsing without implementing objects to support the integration interfaces.
[0017] Additional features and advantages of the invention will be made apparent from the following detailed description of an illustrated embodiment which proceeds with reference to the accompanying drawings.
Brief Description of the Drawings
[0018] FIG. 1 is a block diagram of a computer system that may be used to implement a method and apparatus embodying the invention for unified browsing.
[0019] FIG. 2 is a diagram illustrating a browsing system including the computer of FIG. 1 for unified browsing according to an illustrated embodiment of the invention.
[0020] FIG. 3 is a block diagram of typical data structures for an object in the computer system of FIG. 1.
[0021] FIG. 4 is a block diagram of software components that support binding to a named object using a moniker.
[0022] FIG. 5 is a process flow diagram of a binding process performed by the moniker of FIG. 4.
[0023] FIG. 6 is a block diagram of software components showing a client program using and asynchronous moniker to bind to a named object.
[0024] FIG. 7 is a block diagram of software components showing a client program using a URL moniker to bind to a URL named object.
[0025] FIGS. 8A-8B is a flow chart of the binding process implemented by a method of the URL moniker.
[0026] FIG. 9 is a block diagram of a software component architecture for unified hyperlink navigation in the computer of FIG. 1 according to a further illustrated embodiment of the invention.
[0027] FIG. 10 is a flow chart of a simple hyperlink navigation process performed in the hyperlink navigation architecture of FIG. 9.
[0028] FIG. 11 is a flowchart of a full hyperlink navigation process performed in the hyperlink navigation architecture of FIG. 11.
[0029] FIG. 12 is a view of a hyperlink navigation toolbar used in a browser frame of the browsing system of FIG. 2, and in hyperlink frames of the software component architecture of FIG. 9.
Detailed Description of the Illustrated Embodiments
[0030] 1. Browser Overview
[0031] 2. Object Overview
[0032] 3. Document Object and Server Overview
[0033] 4. Moniker Overview
[0034] 5. Asynchronous Monikers
[0035] 5.1 Asynchronous and Synchronous Binding Selection
[0036] 5.2 Asynchronous and Synchronous Storage
[0037] 5.3 Data-pull and Data-push models
[0038] 5.4 The IBinding Interface
[0039] 5.4.1 The IBinding:Abort Function
[0040] 5.4.2 The IBinding::Suspend Function
[0041] 5.4.3 The IBinding::Resume Function
[0042] 5.4.4 The IBinding::SetPriority Function
[0043] 5.4.5 The IBinding::GetPriority Function
[0044] 5.5 The IBindStatusCallback Interface
[0045] 5.5.1 The BINDVERB Enumeration
[0046] 5.5.2 The BINDINFOF Enumeration
[0047] 5.5.3 The BINDINFO Structure
[0048] 5.5.4 The BSCO_OPTION Enumeration
[0049] 5.5.5 The BINDF Enumeration
[0050] 5.5.6 The BSCF Enumeration
[0051] 5.5.7 The BINDSTATUS Enumeration
[0052] 5.5.8 The IBindStatusCallback::QueryInterface Function
[0053] 5.5.9 The IBindStatusCallback::GetBindInfo Function
[0054] 5.5.10 The IBindStatusCallback::OnStartBinding Function
[0055] 5.5.11 The BindStatusCallback::GetPriority Function
[0056] 5.5.12 The IBindStatusCallback::OnProgress Function
[0057] 5.5.13 The IBindStatusCallback::OnDataAvailable Function
[0058] 5.5.14 The IBindStatusCallback::OnObjectAvailable Function
[0059] 5.5.15 The IBindStatusCallback:: OnLowResource Function
[0060] 5.5.16 The IBindStatusCallback::OnStopBinding Function
[0061] 5.6 The IPersistMoniker Interface
[0062] 5.6.1 The IPersistMoniker::IsDirty Function
[0063] 5.6.2 The IPersistMoniker:: Load Function
[0064] 5.6.3 The IPersistMoniker::Save Function
[0065] 5.6.4 The IPersistMoniker::SaveCompleted
[0066] 5.6.5 The IPersistMoniker::GetCurMoniker Function
[0067] 5.7 API Functions for Asynchronous Monikers
[0068] 5.7.1 The CreateAsyncBindCtx API Function
[0069] 5.7.2 The RegisterBindStatusCallback API Function
[0070] 5.7.3 The RevokeBindStatusCallback API Function
[0071] 5.7.4 The IsAsyncMoniker API Function
[0072] 6. URL Monikers
[0073] 6.1 Media-type Negotiation with the URL Moniker
[0074] 6.1.1 The RegisterMediaTypes API Function
[0075] 6.1.2 The CreateFormatEnumerator API Function
[0076] 6.1.3 The RegisterFormatEnumerator API Function
[0077] 6.1.4 The RevokeFormatEnumerator API Function
[0078] 6.1.5 The CreateURLMoniker API Function
[0079] 6.2 URL Moniker Functions
[0080] 6.2.1 The URL Moniker-IUnknown::QueryInterface Function
[0081] 6.2.2 The URL Moniker-IPersist: :GetClassID Function
[0082] 6.2.3 The URL Moniker-IPersistStream::IsDirty Function
[0083] 6.2.4 The URL Moniker-IPersistStream::Load Function
[0084] 6.2.5 The URL Moniker-IPersistStream::Save Function
[0085] 6.2.6 The URL Moniker-IPersistStream::GetSize Max Function
[0086] 6.2.7 The URL Moniker-IMoniker::BindToObject Function
[0087] 6.2.8 The URL Moniker-IMoniker::BindToStorageFunction
[0088] 6.2.9 The URL Moniker-IMoniker::Reduce Function
[0089] 6.2.10 The URL Moniker-IMoniker::ComposeWith Function
[0090] 6.2.11 The URL Moniker-IMoniker::Enum Function
[0091] 6.2.12 The URL Moniker-IMoniker::IsEqual Function
[0092] 6.2.13 The URL Moniker-IMoniker::Hash Function
[0093] 6.2.14 The URL Moniker-IMoniker::IsRunning Function
[0094] 6.2.15 The URL Moniker-IMoniker::GetTimeOfLastChange Function
[0095] 6.2.16 The URL Moniker-IMoniker::Inverse Function
[0096] 6.2.17 The URL Moniker-IMoniker::CommonPrefix With Function
[0097] 6.2.18 The URL Moniker-IMoniker::RelativePathTo Function
[0098] 6.2.19 The URL Moniker-IMoniker::GetDisplayName Function
[0099] 6.2.20 The URL Moniker-IMoniker::ParseDisplay Name Function
[0100] 6.2.21 The URL Moniker-IMoniker::IsSystemMoniker Function
[0101] 6.3 Client Extension Services
[0102] 6.4 The IAuthenticate interface
[0103] 6.5 The IHttpNegotiate Interface
[0104] 6.5.1 The IHttpNegotiate::BeginningTransaction Function
[0105] 6.5.2 The IHttpNegotiate::OnHeadersAvailable Function
[0106] 6.5.3 The IHttpNegotiate::OnError Function
[0107] 7. Hyperlink Navigation Architecture
[0108] 7.1 Hyperlink Navigation Overview
[0109] 7.2 Hyperlink Navigation Architecture Overview
[0110] 7.2.1 “Simple” Hyperlinking API Functions
[0111] 7.2.2 Hyperlink Target
[0112] 7.2.3 Hyperlink Object
[0113] 7.2.4 Hyperlink Container and Hyperlink
[0114] 7.2.5 Hyperlink Frame
[0115] 7.2.6 Hyperlink Browse Context
[0116] 7.3 Simple Hyperlinking Process
[0117] 7.4 Full Hyperlink Navigation Process
[0118] 7.5 Hyperlinking Interfaces
[0119] 7.6 Hyperlinking Architecture Data Structures
[0120] 7.6.1 The HLNF Enumeration
[0121] 7.6.2 The HLINKWHICHMK Enumeration
[0122] 7.6.3 The HLINKGETREF Enumeration
[0123] 7.6.4 The HLFNAMEF Enumeration
[0124] 7.6.5 The HLINKMISC Enumeration
[0125] 7.6.6 The HLITEM Structure
[0126] 7.6.7 The HLBWIF Enumeration
[0127] 7.6.8 The HLBWINFO Structure
[0128] 7.6.9 The HLID Constants
[0129] 7.6.10 The HLQF Enumeration
[0130] 7.6.11 The CF HYPERLINK Clipboard Format
[0131] 7.6.12 The HLSR Enumeration
[0132] 7.7 Hyperlinking Architecture API Functions
[0133] 7.7.1 The HlinkCreateBrowseContext API Function
[0134] 7.7.2 The HlinkQueryCreateFromData API Function
[0135] 7.7.3 The HlinkCreateFromData API Function
[0136] 7.7.4 The HlinkCreateFromMoniker API Function
[0137] 7.7.5 The HlinkCreateFromString API Function
[0138] 7.7.6 The HlinkGetSpecialReference API Function
[0139] 7.7.7 The HlinkSetSpecialReference API Function
[0140] 7.7.8 The HlinkNavigateToStringReference API Function
[0141] 7.7.9 The HlinkNavigate API Function
[0142] 7.7.10 The HlinkOnNavigate API Function
[0143] 7.8 The IHlinkSite Interface
[0144] 7.8.1 The IHlinkSite::GetMoniker Function
[0145] 7.8.2 The IHlinkSite::GetInterface Function
[0146] 7.8.3 The IHlinkSite::OnNavigationComplete Function
[0147] 7.9 The IHlink Interface
[0148] 7.9.1 The IHlink::SetHlinkSite Function
[0149] 7.9.2 The IHlink::GetHlinkSite Function
[0150] 7.9.3 The IHlink::GetMonikerReference Function
[0151] 7.9.4 The IHlink::GetStringReference Function
[0152] 7.9.5 The IHlink::GetFriendlyName Function
[0153] 7.9.6 The IHlink::SetFriendlyName Function
[0154] 7.9.7 The IHlink::GetTargetFrameName Function
[0155] 7.9.8 The IHlink::SetTargetFrameName Function
[0156] 7.9.9 The IHlink::GetAdditionalParams Function
[0157] 7.9.10 The IHlink::SetAdditionalParams Function
[0158] 7.9.11 The IHlink:Navigate Function
[0159] 7.9.12 The IHlink::GetMiscStatus Function
[0160] 7.10 The IHlinkTarget Interface
[0161] 7.10.1 The IHlinkTarget::SetBrowseContext Function
[0162] 7.10.2 The IHlinkTarget::GetBrowseContext Function
[0163] 7.10.3 The IHlinkTarget::Navigate Function
[0164] 7.10.4 The IHlinkTarget::GetMoniker Function
[0165] 7.10.5 The IHlinkTarget::GetFriendlyName Function
[0166] 7.11 The IHlinkFrame Interface
[0167] 7.11.1 The IHlinkFrame::SetBrowseContext Function
[0168] 7.11.2 The IHlinkFrame::GetBrowseContext Function
[0169] 7.11.3 The IHlinkFrame::Navigate Function
[0170] 7.11.4 The IHlinkFrame::OnNavigate Function
[0171] 7.12 The IHlinkBrowseContext Interface
[0172] 7.12.1 The IHlinkBrowseContext::Register Function
[0173] 7.12.2 The IHlinkBrowseContext::GetObject Function
[0174] 7.12.3 The IHlinkBrowseContext::Revoke Function
[0175] 7.12.4 The IHlinkBrowseContext::SetBrowse WindowInfo Function
[0176] 7.12.5 The IHlinkBrowseContext::GetBrowse WindowInfo Function
[0177] 7.12.6 The IHlinkBrowseContext::EnumNavigationStack Function
[0178] 7.12.7 The IHlinkBrowseContext::QueryHlink Function
[0179] 7.12.8 The IHlinkBrowseContext::GetHlink Function
[0180] 7.12.10 The IHlinkBrowseContext::SetCurrent Hlink Function
[0181] 7.12.10 The IHlinkBrowseContext::OnNavigateHlink Function
[0182] 7.12.11 The IHlinkBrowseContext::Clone Function
[0183] 1. Computer Overview
[0184] Referring to FIG. 1, an operating environment for an illustrated embodiment of the present invention is a computer system 20 with a computer 22 that comprises at least one high speed processing unit (CPU) 24, in conjunction with a memory system 26, an input device 28, and an output device 30. These elements are interconnected by at least one bus structure 32.
[0185] The illustrated CPU 24 is of familiar design and includes an ALU 34 for performing computations, a collection of registers 36 for temporary storage of data and instructions, and a control unit 38 for controlling operation of the system 20. The CPU 24 may be a processor having any of a variety of architectures including Alpha from Digital, MIPS from MIPS Technology, NEC, IDT, Siemens, and others, x86 from Intel and others, including Cyrix, AMD, and Nexgen, and the PowerPc from IBM and Motorola.
[0186] The memory system 26 generally includes high-speed main memory 40 in the form of a medium such as random access memory (RAM) and read only memory (ROM) semiconductor devices, and secondary storage 42 in the form of long term storage mediums such as floppy disks, hard disks, tape, CD-ROM, flash memory, etc. and other devices that store data using electrical, magnetic, optical or other recording media. The main memory 40 also can include video display memory for displaying images through a display device. Those skilled in the art will recognize that the memory 26 can comprise a variety of alternative components having a variety of storage capacities.
[0187] The input and output devices 28, 30 also are familiar. The input device 28 can comprise a keyboard, a mouse, a physical transducer (e.g., a microphone), etc. The output device 30 can comprise a display, a printer, a transducer (e.g., a speaker), etc. Some devices, such as a network interface or a modem, can be used as input and/or output devices.
[0188] As is familiar to those skilled in the art, the computer system 20 further includes an operating system and at least one application program. The operating system is the set of software which controls the computer system's operation and the allocation of resources. The application program is the set of software that performs a task desired by the user, using computer resources made available through the operating system. Both are resident in the illustrated memory system 26.
[0189] In accordance with the practices of persons skilled in the art of computer programming, the present invention is described below with reference to acts and symbolic representations of operations that are performed by computer system 20, unless indicated otherwise. Such acts and operations are sometimes referred to as being computer-executed. It will be appreciated that the acts and symbolically represented operations include the manipulation by the CPU 24 of electrical signals representing data bits which causes a resulting transformation or reduction of the electrical signal representation, and the maintenance of data bits at memory locations in memory system 26 to thereby reconfigure or otherwise alter the computer system's operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, or optical properties corresponding to the data bits.
[0190] 1. Browser Overview
[0191] In a browsing environment 50 of an illustrated embodiment of the invention shown in FIG. 2, the computer 20 (also shown in FIG. 1) runs software, referred to herein as a “browser,” for unified browsing of electronic documents and other data from local sources (e.g., the secondary storage 42 of FIG. 1) and from a remote computer network 52. The browser can be integrated with the operating system software, or can be a separate application software. The illustrated browser is implemented by the software as an OLE object (described below).
[0192] The illustrated remote computer network 52 is the Internet, which is described in the Background and Summary of the Invention above. In the illustrated browsing environment 50, the computer 20 connects to the computer network 52 over a telephone line 54 with a modem 56. Other physical connections to the computer network alternatively can be used, such as an ISDN, T1 or like high speed telephone line and modem, a television cable and modem, a satellite link, an optical fiber link, an Ethernet or other local area network technology wire and adapter card, radio or optical transmission devices, etc. The invention can alternatively be embodied in a browsing environment for other public or private computer networks, such as a computer network of a commercial on-line service or an internal corporate local area network (LAN), an intranet, or like computer network.
[0193] Documents for browsing with the illustrated browser can reside as files of a file system stored in the computer's secondary storage 42 (FIG. 1), or reside as resources at a remote computer 58 (also referred to as a “site”) connected to the computer network 52, such as a world-wide web site on the Internet. The illustrated document 60 residing at the site 58 conforms with HTML standards, and may include extensions and enhancements of HTML standards. However, the illustrated browser also can browse documents having other data formats (e.g., Microsoft® Word documents, etc.) from the computer 20 or remote computer 58.
[0194] In conformance with HTML, the illustrated document 60 can incorporate other additional information content 62, such as images, audio, video, executable programs, etc. (hereafter simply “images” 62), which also reside at the remote computer 58. The document 60 and images 62 preferably are stored as files in a file system of the remote computer 58. The document 60 incorporates the images 62 using HTML tags that specify the location of files or other Internet resource containing the images on the Internet 52.
[0195] When used for browsing documents, the illustrated browser displays the document in a window 68 or rectangular area of the computer's display 30 allocated to the browser by the operating system. The illustrated window 68 comprises a frame 70, a document display area 72, and user interface controls 74. The browser provides the document display area 72 for displaying the document.
[0196] The browser and other client applications within the computer 20 preferably work with documents (which have data formats other than those native to the browser or client application) by encapsulating the document's data into an associated object, and integrating with the object using pre-defined interfaces as described more fully below. These document objects include the code to work with the document's data, including code to display the document data in the document display area 72. The browser thus operates as a host or container of document objects, by providing a window and frame which includes a document display area in which a hosted document object can display its document. Working with documents encapsulated as document objects allows full use of all the features described below.
[0197] Alternatively, the browser or other client application can work with a document by launching an application program associated with the document, and causing the associated application program to load the document and perform a specified operation on the document. In the Microsoft Windows® operating system, this is done by looking up the application program associated with the document's file name extension in the system registry, (e.g., “.doc” for Microsoft® Word documents, “.vsd” for Shapeware's VISIO drawings, etc.) and a text string command for directing the program to perform a desired operation. The application program associated with a document also may be identified in the Microsoft Windows® operating system by matching a bit pattern at specific offset into the file as also specified in the system registry. The browser or other client application patches the document's file name into the text string command, and invokes the operating system's shell execute service to execute the command. Shell execute is a well known Windows® operating system service which issues a text string as a command to the operating system's command interpreter (i.e., the “command.com” program in the Windows® operating system). The text string generally is in the form of an MS-DOS command, which specifies a path and file name of the associated application program's executable file, a flag for specifying the desired operation, and the document's path and file name. The command interpreter responds by parsing the text string, loading the application program specified in the text string, and passing the flag and the document's path and file name as command line arguments into the application program. The application program then “opens” (i.e., loads) the document and performs the operation specified by the flag.
[0198] Referring to FIG. 12, the user interface controls of the illustrated browser include a hyperlink navigation toolbar 480 for use in controlling hyperlink navigation. The illustrated hyperlink navigation toolbar 480 includes a button bar 482 and an address entry bar 484. The user can navigate to a desired document or other application in the illustrated browser by clicking on a hyperlink contained in the document which is currently displayed within the browser frame, or by entering a name (e.g., a URL address or file system path name) for the document in the address entry bar. Other operations associated with hyperlink navigation are activated from the toolbar. A menu bar with drop down menus also can be included for activating other browser operations.
[0199] The button bar 482 has button controls 490-496 for activating various hyperlink navigation operations. The button control 490 is a “go back” button which operates to navigate to an immediately preceding document or application program in a sequentially ordered history (described more fully below) of previously navigated documents and applications. The button control 491 is a “go forward” button which causes navigation to a next document or application in the history. The button control 492 is a stop button which operates to halt retrieval of a document during hyperlink navigation. The button control 493 is a refresh button which causes the browser to redisplay the current document. The button control 494 is a home button which causes the browser to navigate to a user-defined default start document (which may, for example, be a home page on the Internet such as the Microsoft Network home page at the URL, “http://www.msn.com”). The button control 495 is a search button which operates to initiate a search using an Internet search engine on user input keywords. The button control 496 is a favorites button which accesses a favorites list feature of the browser, which is a user defined list of documents. The address entry bar 484 includes a text entry box 498 and a drop down list control 499. The user can enter a name of a document for the browser to retrieve in the text entry box 498. The drop down button 499 operates to display a list of most recently navigated documents from the history. The user can navigate to a document by selecting it from the drop down list.
[0200] In the illustrated browser, the hyperlink navigation toolbar 480 has a default position within the browser window 68 in a horizontal orientation under a title bar portion of the frame 70 (FIG. 2). However, the user can move the toolbar to other optional positions (e.g., in a vertical orientation at the right or left edge of the frame, in a horizontal orientation at a bottom edge of the frame, or in a moveable sub-window) by editing the toolbar's properties. In the illustrated embodiment, the user edits the properties by selecting a customize menu command. This opens a customize dialog box with user interface controls for setting the toolbar's properties.
[0201] 2. Object Overview
[0202] Referring to FIG. 2, the illustrated embodiment of the invention utilizes objects which conform to the component object model (COM) of Microsoft Corporation's OLE. For a detailed discussion of OLE see Inside OLE, Second Editionby Kraig Brockschmidt, Microsoft Press, Redmond, Wash. 1995. A brief overview of objects in OLE and associated terminology is provided below before discussing the details of the illustrated embodiment.
[0203] An object is an instance of a programmer-defined type referred to as a class, which exhibits the characteristics of data encapsulation, polymorphism and inheritance. Data encapsulation refers to the combining of data (also referred to as properties of an object) with methods that operate on the data (also referred to as member functions of an object) into a unitary software component (i.e., the object), such that the object hides its internal composition, structure and operation and exposes its functionality to client programs that utilize the object only through one or more interfaces. An interface of the object is a group of semantically related member functions of the object. In other words, the client programs do not access the object's data directly, but must instead call functions on the object's interfaces to operate on the data.
[0204] Polymorphism refers to the ability to view (i.e., interact with) two similar objects through a common interface, thereby eliminating the need to differentiate between two objects. Inheritance refers to the derivation of different classes of objects from a base class, where the derived classes inherit the properties and characteristics of the base class (which for purposes of OLE are the interfaces of the base class).
[0205] OLE's COM specification defines binary standards for objects and their interfaces which facilitate the integration of software components. According to the COM specification, a typical object 80 is represented in the computer system 20 (FIG. 1) by an instance data structure 82, a virtual function table 84, and member functions 86-88. The instance data structure 82 contains a pointer 90 to the virtual function table 84 and data 92 (also referred to as data members, or properties of the object). A pointer is a data value that holds the address of an item in memory. The virtual function table 84 contains entries 96-98 for the member functions 86-88. Each of the entries 96-98 contains a reference to the code 86-88 that implements the corresponding member function.
[0206] The pointer 90, the virtual function table 84, and the member functions 86-88 implement an interface of the object 80. Client programs interact with the object 80 by obtaining a pointer (referred to as an interface pointer) to the pointer 90 of the virtual function table 84. OLE includes a type definition of an interface pointer which allows client programs to call member functions on the interface by name through the interface pointer and provides type checking on the function's arguments, as expressed in the following code (in the C++ programming language):
[0207] pInterface->MemberFunction( . . .)
[0208] By convention, the interfaces of an object are illustrated graphically as a plug-in jack as shown for the document object in FIG. 3. Also, Interfaces conventionally are given names beginning with a capital “I.” Objects can include multiple interfaces which are implemented with one or more virtual function tables. The member function of an interface is denoted as “IInterfaceName::FunctionName.”
[0209] The object 80 conforming to the COM specification exhibits data encapsulation by exposing its interfaces (semantic groupings of its member functions) to client programs. The client programs interact with the object 80 by calling the member functions 86-88 on a particular interface of the object, but do not directly manipulate the object's data. The object 80 also exhibits polymorphism and inheritance in that the object 80 can provide interfaces in common with a base class and other similar objects, so that client programs can interact with each of the objects in the same manner by calling member functions of the interface that the objects have in common.
[0210] 3. Document Object and Server Overview
[0211] Referring now to FIG. 5, the virtual function table 84 and member functions 86-88 of the object 80 are provided by a server application program 100 which is stored in the computer system 20 (FIG. 1) as an executable program file (with a “.exe” file name extension) or as a dynamic link library file (with a “.dll” file name extension). Dynamic link library files are loaded, dynamically linked, and executed by the Windows® operating system in a same process with a client application program. Executable program files are loaded by the operating system as a separately executing process. In accordance with OLE, the server application 100 includes code for the virtual function table 84 (FIG. 3) and member functions 86-88 (FIG. 3) of the classes that it supports, and also includes a class factory that generates the instance data structure 82 (FIG. 3) for an object of the class.
[0212] A server application can be written by a programmer to support a particular class of object that contains any desired data. More specifically, a programmer can write server applications which provide objects that contain the data of a particular variety of computer document (e.g., document 60 of FIG. 2), such as a text document, spreadsheet, drawing, etc., or that contain data for part of a computer document, such as a range of spreadsheet cells, a paragraph of a text document, etc. These objects which contain document data are referred to herein as document objects. For example, software application programs such as Microsoft® Word can be written as a server application in which the application program's documents are represented as OLE objects. A server application also can be written for representing the HTML document 60 and images 62 (FIG. 2) as OLE objects. This allows other client programs 104 (such as the unified browsing software program illustrated in FIG. 2) and objects to interact with the document through interfaces of the document object.
[0213] The document objects in the illustrated embodiment of the invention conform to an extension of OLE objects known as DocObjects. DocObjects are used by the binder application program in the Microsoft® Office 95 product, and are described in more detail in a pending U.S. patent application (a copy of which is attached as Exhibit A hereto). DocObjects are document objects that generate a view of their documents that can be displayed stand-alone in a display area of a frame provided by a hosting frame object (e.g., the document display area 72 in the frame 70 provided by the browser of FIG. 2).
[0214] For the client program 104 to interact with the document object 80 provided by the server application 100, the server application must first create the object (i.e., instantiate an object of a class supported by the server application) and the client 104 must gain an interface pointer to the object 80. In OLE, the client program 104 realizes these events using services provided by OLE and a set of standard object interfaces defined by COM based on class and interface identifiers assigned to the object's class and interfaces. More specifically, the services are available to client programs as application programming interface (API) functions provided in the COM library, which is part of a component of the Windows® operating system in a file named “OLE32.DLL.” In OLE, classes of objects are uniquely associated with class identifiers (“CLSIDs”). Class identifiers are 128-bit globally unique identifiers (“GUID”) that the programmer creates with an OLE service named “CoCreateGUID” and assigns to the respective classes. The interfaces of an object are associated with interface identifiers (“IIDs”).
[0215] In particular, the COM library provides an API function, “CoCreatelnstance,” that the client program 104 can call to request creation of an object to encapsulate a particular documents data using a CLSID associated with the data. The CoCreatelnstance API function creates the object and returns a pointer of the requested interface to the client program.
[0216] Once the client program 104 has obtained a first interface pointer to the object 80, the client obtains pointers to other desired interfaces of the object using the interface identifier associated with the desired interface. COM defines several standard interfaces generally supported by OLE objects including the IUnknown interface. This interface includes a member function named “QueryInterface.” The QueryInterface function can be called with an interface identifier as an argument, and returns a pointer to the interface associated with that interface identifier. By convention, the IUnknown interface's member functions are included as part of each interface on an object. Thus, any interface pointer that the client obtains to an interface of the object 80 can be used to call the QueryInterface function.
[0217] In a typical situation, however, the only information that the client program 104 has to reference a particular document is a textual name, such as a file name or an Internet URL. In the case of a file name, the COM library provides API functions (e.g., “GetClassFile,” “ReadClassStg” and “ReadClassStm”) for obtaining a CLSID associated with the file. These functions, however, are specific to document data that is stored as a file in a computer's local storage.
[0218] 4. Moniker Overview
[0219] With reference to FIGS. 4 and 5, the client program 104 also can gain access (i.e., a pointer to an interface) to the object 80 which encapsulates some desired data based on a name that references the object using a moniker 120. The moniker 120 generally is provided by the COM library of the operating system 114. Alternatively, the moniker may be provided by the server application associated with the object 80. The system 114 includes API functions which the client program 104 calls to have a moniker created for a given name. In OLE, there are four standard classes of monikers, i.e., file moniker, item moniker, pointer moniker, and anti-moniker, which are described more fully in the book, Inside OLE, second edition,supra. The API functions for creating a moniker of these standard moniker classes are summarized in the following table:
| TABLE 1 |
|---|
| OLE Moniker APIs. |
[0220] For creating a moniker based on a user-provided name, the system 114 also provides an OLE API function called MkParseDisplayName, which has the following form:
[0221] HRESULT MkParseDisplayName(IBindCtx *pbc, LPCWSTR pszName, ULONG *pchEaten, IMoniker **ppmk)
[0222] The MkParseDisplayName API function parses a text string (the parameter “pszName”) into a moniker. The text string can have one of two initial patterns: a uniform naming convention (UNC) path name (a conventional file system path name such as “c:\directory\file”), or the character “@” followed by a program identifier (ProgID) of a server application. In the case of a UNC path name, the API function creates a file moniker and calls the file moniker's “ParseDisplayName” function (described below) to parse the text string. In the case of a text string with the “@” character and ProgID, the API function creates an object based on a CLSID associated with the ProgID in the operating system's registry database and calls a “ParseDisplayName” member function on an “IParseDisplayName” interface of that object, which is defined as follows:
[0223] interface IParseDisplayName: IUnknown {
[0224] HRESULT ParseDisplayName(IBindContext *pbc,
[0225] LPOLESTR pszDisplayName, ULONG
[0226] *pchEaten, IMoniker **ppmkOut);
[0227] };
[0228] By effectively plugging in a new name-to-moniker parser in this way, the MkParseDisplayName API can be extended to create new classes of monikers.
[0229] The moniker 120 exposes a set of member functions to the client 104 through an interface 124, designated IMoniker, which is defined as follows:
[0230] interface IMoniker: public IPersistStream {
[0231] public:
[0232] HRESULT BindToObject(IBindCtx *pbc, IMoniker *pmkToLeft,
[0233] REFIID riidResult, void *ppvResult);
[0234] HRESULT BindToStorage(IBindCtx *pbc, IMoniker
[0235] *pmkToLeft, REFIID riid, void **ppvObj);
[0236] HRESULT Reduce(IBindCtx *pbc, DWORD
[0237] dwReduceHowFar, IMoniker **ppmkToLeft, IMoniker
[0238] **ppmkReduced);
[0239] HRESULT ComposeWith(IMoniker *pmkright, BOOL
[0240] fOnlylfNotGeneric, IMoniker **ppmkcomposite);
[0241] HRESULT Enum(BOOL fForward, IEnumMoniker
[0242] **ppenumMoniker);
[0243] HRESULT IsEqual(IMoniker *pmkOtherMoniker);
[0244] HRESULT Hash(DWORD *pdwHash);
[0245] HRESULT IsRunning(IBindCtx *pbc, IMoniker *pmkToLeft,
[0246] IMoniker *pmkNewlyRunning);
[0247] HRESULT GetTimeOfLastChange(IBindCtx *pbc, IMoniker
[0248] *pmkToLeft, FILETIME *pFileTime);
[0249] HRESULT Inverse(IMoniker **pmk);
[0250] HRESULT CommonPrefixWith(IMoniker *pmkOther, IMoniker
[0251] **ppmkPrefix);
[0252] HRESULT RelativePathTo(IMoniker *pmkOther, IMoniker
[0253] **ppmkRelPath);
[0254] HRESULT GetDisplayName(IBindCtx *pbc, IMoniker
[0255] *pmkToLeft, LPOLESTR *ppszDisplayName);
[0256] HRESULT ParseDisplayName(IBindCtx *pbc, IMoniker
[0257] *pmkToLeft, LPOLESTR *pszDisplayName, ULONG
[0258] *pchEaten, IMoniker **ppmkOut);
[0259] HRESULT IsSystemMoniker(DWORD *pdwMksys);
[0260] };
[0261] As indicated in the above interface definition, the IMoniker interface is derived from the IPersistStream interface, which is a well known OLE interface for objects that can read and write their state persistently as a data stream or file in the computer's secondary storage 42 (FIG. 1). This means that the moniker 120 also includes member functions to support the IPersistStream interface, which allows the client to store and load the moniker 120 from the secondary storage.
[0262] The member functions which the moniker 120 exposes through the IMoniker interface 124 include two functions, BindToObject and BindToStorage (herein collectively referred to as BindToXxx), which the client 104 calls to bind to the named object 80. The BindToObject function performs binding by instantiating the named object 80 in the memory 40 (FIG. 1) of the computer, and returns an interface pointer of the named object 80 to the client 104. The BindToStorage function performs binding by instantiating the named object 80 onto an OLE storage stream which is stored in the computer's secondary storage 42 (e.g., on the hard drive), rather than into the main memory 40. In the browsing environment 50 illustrated in FIG. 2 for example, the BindToStorage function is used to download a file such as an image or video clip directly onto hard disk storage, whereas the BindToObject function is used to create an instance of an object for an HTML document with code for viewing the document.
[0263] The IMoniker interface 124 also exposes the functions, GetDisplayName and ParseDisplayName, of the moniker 120 to the client 104. The GetDisplayName function returns a human-readable display name of the object 80 which the client can display to the user, such as in a list box control or other user interface element. The display name is a text string that names the object 80, such as a path and file name or an Internet URL. The ParseDisplayName function operates in reverse, creating a moniker based on a text string provided by the client.
[0264] Further details of the moniker's member functions are described in Inside OLE, second edition,supra.
[0265] When calling most of the moniker's member functions, the client program 104 passes a pointer to a bind context 126 as a parameter of the call. The bind context 126 is an object which operates as a central repository of information used globally in the binding process, such as a table of running objects. The bind context 126 has an interface 128, designated IBindCtx, which is defined as follows:
[0266] interface IBindCtx: IUnknown
[0267] {
[0268] HRESULT RegisterObjectBound(IUnknown *pUnk);
[0269] HRESULT RevokeObjectBound(IUnknown *pUnk);
[0270] HRESULT ReleaseBoundObjects(void);
[0271] H RESULT SetBindOptions(BIND_OPTS *pbindopts);
[0272] HRESULT GetBindOptions(BIND_OPTS *pbindopts);
[0273] HRESULT GetRunningobjectTable(IRunningObjectTable
[0274] **ppROT);
[0275] HRESULT RegisterObjectParam(LPOLESTR pszKey, IUnknown *pUnk);
[0276] HRESULT GetObjectParam(LPOLESTR pszKey, IUnknown
[0277] **ppUnk);
[0278] HRESULT EnumOjbectParam(IEnumString **ppEnum);
[0279] HRESULT RevokeObjectParam(LPOLESTR pszKey);
[0280] };
[0281] The bind context 126 is provided by the system 114. The client program 104 creates the bind context 126 by calling a system API function, CreateBindCtx. The client program 104 creates the bind context once, then passes a pointer t o the bind context's IBindCtx interface in calls to the moniker 120. This allows the moniker 120 to retrieve global information stored in the bind context 126 by calling functions on the IBindCtx interface. When called by the client to bind to the named object 80 for example, the moniker 120 can look in the running objects table of the bind context 126 to determine whether the object already exists. If the object exists, the moniker 120 can simply return an interface pointer of the existing object to the client 104, and thus avoid creating the object again. Other uses of the bind context are described in Inside OLE, second edition,supra.
[0282] FIG. 5 illustrates the operation of the moniker 120 performing the binding process for the client program 104 to an interface of the named object 80. In the illustrated example, the client program 104 uses the moniker 120 to bind to the object referenced by a name with code such as the following:
[0283] HRESULT hr;
[0284] IBindCtx* pbc;
[0285] hr=CreatBindCtx(0, &pbc);
[0286] . . .
[0287] IMoniker *pmk;
[0288] IObj1 *pObj;
[0289] GetMonikerSomehow(&pmk);
[0290] hr = pmk->BindToObject(pbc,0, IID_IObj1, &pObj);
[0291] if (hr==S_OK) {
[0292] pObj->SomeFunction(. . . );
[0293] }
[0294] In this example, the named object 80 exposes a member function, SomeFunction, through an IObj1 interface 130, and includes a second interface 131, IObj2. With the above code, the client first creates the bind context 126 which will be used later by the moniker 120 when binding to the named object 80. The client creates the bind context by calling the CreateBindCtx API function of the system 114 as described above. The CreateBindCtx API function returns an interface pointer of the IBindCtx interface 128 to the client 104, which the client stores as the pointer variable 134, pbc.
[0295] The client next creates the moniker 120 which names the object 80 using a moniker creation API function of the system 114 as described above (e.g., MKParseDisplayName). The client is returned an interface pointer of the IMoniker interface 124. In this example code, the client stores this pointer to the IMoniker interface 124 of the moniker 120 as a pointer variable 136, pmk. The client 104 then performs a call 130 to the BindToObject function on the IMoniker interface 124 of the moniker 120 to bind to the named object 80. In the call 140, the client passes an interface identifier (IID_IObj1) to request binding to a particular interface (the IObj1 interface 130) of the named object 80.
[0296] In the moniker's BindToObject function, the moniker 120 includes code which launches the object's server application program 100, requests creation of the named object, and queries for a pointer to the interface requested by the client. The moniker 120 typically performs these steps with calls 142 to the GetClassFile and CoCreateInstance API functions described above, and to the QueryInterface member function of the object 80 to query for the requested interface of the object as also described above. As a result, the object 80 is instantiated by its class factory in the server application 100, and returns (144) a pointer of the requested interface (the IObj1 interface 130 in this example) of the named object 80 to the moniker 120. The moniker 120, in turn, returns (146) the object's interface pointer to the client program 104. Whereupon, the client program can directly call (148) member functions on the interface of the named object 80. At this point, the binding process is complete and the moniker 120 is no longer needed by the client program 104 to access the named object 80.
[0297] 5. Asynchronous Monikers
[0298] In an illustrated embodiment of the invention shown in FIG. 6, a client program (hereafter “client”) 152 uses an asynchronous moniker 150 to asynchronously bind to a named object 154. The asynchronous moniker 150 is an instance of an asynchronous moniker class which is derived from the moniker class and supports the IMoniker interface 124. Asynchronous binding effectively retrieves data from its source as a background process which allows the client 152 to continue execution. Since the client 152 is not blocked, the client's user interface remains responsive during the binding process. This is particularly useful for loading objects having data from slow sources, such as the Internet and other remote networks with high latency and slow data transfer connections. The client 152 thus is able to more uniformly browse data from fast and slow sources while maintaining the user perception of equivalent responsiveness and quality of service.
[0299] Similar to the use of standard OLE monikers described above, the client 152 creates an asynchronous bind context 156, and the asynchronous moniker 150 by calling API functions (specifically, the CreateAsyncBindCtx API function described below, and the MkParseDisplayName API functions described above) provided by an operating system component 158 (specifically a component such as the COM library 114 of FIG. 4, which additionally implements the asynchronous moniker API functions described below). The asynchronous bind context supports IBindCtx interface 128 of the bind context 126 (FIG. 4). The client 152 then calls the BindToObject or BindToStorage function on the IMoniker interface 124 of the asynchronous moniker 150 to initiate the asynchronous binding process.
[0300] The asynchronous binding process involves additional communication or “handshaking” between the client 152 and asynchronous moniker 150 not performed in the synchronous binding process by standard OLE monikers (e.g., the moniker 120). In the asynchronous binding process, the asynchronous moniker 150 returns control immediately to the client 152 from the client's call (e.g., call 140 of FIG. 5) to one of the asynchronous moniker's binding functions (e.g., BindToObject and BindToStorage). After the call returns, instantiation of the named object 154 and loading of the object's data proceeds. Meanwhile, the client and asynchronous binding process continue communicating so that the client remains informed of the progress of loading the data and can interrupt or terminate loading of the data.
[0301] This handshaking between the client 152 and the asynchronous binding process is effected using two additional interfaces, an IBinding interface 160 and an IBindStatusCallback interface 162. In the illustrated embodiment of the invention, the IBinding interface 160 is an interface of a binding object 164 which is provided by the asynchronous moniker 150. The client 152 implements a bind-status-callback object 166 which supports the IBindStatusCallback interface 162.
[0302] Prior to initiating the asynchronous binding process with a call to the IMoniker interface 124 of the asynchronous moniker 150, the client 152 registers its bind-status-callback object 166 with the asynchronous bind context via the RegisterBindStatusCallback API function described more fully below. When the client thereafter calls the IMoniker::BindToObject or IMoniker::BindToStorage function as shown in FIG. 5 and described above, the client 152 passes an interface pointer of the bind context's IBindCtx interface 128 to the asynchronous moniker 150. In the IMoniker::BindToxxx function, the asynchronous moniker 150 looks up the client's bind-status-callback object 164, creates the binding object 164, and hooks together the binding object 164 and the client's bind-status-callback object 166 by passing an interface pointer of the IBinding interface 160 to the bind-status-callback object 166 (with a call to the bind-status-callback object's IBindStatusCallback::OnStartBinding function described more fully below). The asynchronous moniker 150 then returns control to the client 152 from the IMoniker::BindToxxx function, and allows the binding object 164 to proceed with the binding process with the binding object 164 and bind-status-callback object 166 communicating directly.
[0303] 5.1 Asynchronous and Synchronous Binding Selection
[0304] In the illustrated embodiment, the client 152 can determine whether any particular moniker supports asynchronous binding (i.e., is an asynchronous moniker) by calling an IsAsyncMoniker API function (described below). The client 152 can further control whether the asynchronous moniker 150 performs binding asynchronously or synchronously by setting a BINDF_ASYNCHRONOUS flag when the asynchronous moniker 150 calls an IBindStatusCallback::GetBindInfo function (described below) of the client's bind-status-callback object 166 at the beginning of the bind operation.
[0305] When the client 152 specifies asynchronous binding, the asynchronous moniker 150 does not return an object or storage pointer from the client's call to the IMoniker::BindToObject or IMoniker::BindToStorage function. Instead, the asynchronous moniker 150 returns the value, MS_S_ASYNCHRONOUS, and a NULL pointer. The client 152 then waits to receive the requested object or storage from the asynchronous moniker in a call to the client's IBindStatusCallback::OnObjectAvailable or IBindStatusCallback::OnDataAvailable function (described below).
[0306] On the other hand, if the client does not set the BINDF_ASYNCHRONOUS flag, the asynchronous moniker synchronously binds the object or storage, and returns the object or storage from the client's call to the asynchronous moniker's IMoniker::BindToObject or IMoniker::BindToStorage function.
[0307] 5.2 Asynchronous and Synchronous Storage
[0308] In a call to the IBindStatusCallback::OnDataAvailable function (described below) during asynchronous binding to storage, the asynchronous moniker 150 also may return an asynchronous storage object. The asynchronous storage object may allow access to some of the data being bound while the binding is still in progress. The client 152 can choose between two modes for the asynchronous storage object: blocking and non-blocking. If data is not yet available in the blocking mode (the default), the client's call to the asynchronous storage object blocks until the data arrives. In the non-blocking mode, the asynchronous storage object returns an error value, E_PENDING, to the client's call when data is not yet available. In response, the client waits for further notifications to its IBindStatusCallback::OnDataAvailable function before retrying the operation. The client 152 can choose between a synchronous (blocking) and asynchronous (non-blocking) storage by choosing whether or not to set the BINDF_ASYNCSTORAGE flag in the pgrfBINDF value which the client returns from the IBindStatusCallback::GetBindInfo function (described below) to the asynchronous moniker 150.
[0309] 5.3 Data-pull and Data-push Models
[0310] The client 152 can choose between a data-pull and data-push model for driving the asynchronous binding in the asynchronous moniker's IMoniker::BindToStorage function, and receiving asynchronous notifications. In the data-pull model, the client 152 drives the bind operation. The asynchronous moniker 150 only provides data to the client 152 when the client reads the data. Specifically, this means that beyond the asynchronous moniker's first call to the IBindStatusCallback::OnDataAvailable function (described below), the asynchronous moniker 150 will not provide any data to the client unless the client has consumed all of the data that is already available. Because the asynchronous moniker 150 only downloads data as it is requested, the client nevertheless should read the data in a timely manner. In the case of downloading data from Internet for example, the bind operation may fail if the client 152 waits too long before requesting more data.
[0311] On the other hand, in a data-push model, the asynchronous moniker 150 will drive the bind operation and continuously notifies the client whenever new data is available (i.e., by calling the client's IBindStatusCallback::OnDataAvailable function). In such cases, the client 152 may choose whether or not to read the data at any point during the bind operation, but the asynchronous moniker continues to drive the bind operation until completion.
[0312] 5.4 The IBinding Interface
[0313] The IBinding interface 160 is implemented by the asynchronous moniker 150 on the binding object 164, which is a separate object that the asynchronous moniker 150 creates on a per-bind operation basis. The IBinding interface 160 exposes member functions of the binding object 164 which allow control of the bind operation performed by the binding object. The asynchronous moniker 164 provides the client 152 with access to the IBinding interface 160 by passing a pointer of the IBinding interface to the client's bind-status-callback object 166 via a call to the IBindStatusCallback::OnStartBinding function described below.
[0314] The IBinding interface 160 is defined as follows:
[0315] interface IBinding: IUnknown {
[0316] HRESULT Abort(void);
[0317] HRESULT Suspend(void);
[0318] HRESULT Resume(void);
[0319] HRESULT SetPriority([in] LONG nPriority);
[0320] HRESULT GetPriority([out] LONG* pnPriority);
[0321] };
[0322] 5.4.1 The IBinding:Abort Function
[0323] The IBinding::Abort member function permanently aborts the bind operation. After aborting the bind operation, the client may still receive some notifications about the binding.
[0324] An aborted bind operation will result in a call to the IBindStatusCallback::OnStopBinding function (described below) with a corresponding error code. Alternatively, the aborted bind operation results in a failure of the client's call to the IMoniker::BindToObject/BindToStorage function in the situation where that call has not previously returned. At this point the bind operation is officially complete and the client must release any pointers obtained during the binding.
[0325] The return values of the illustrated IBinding::Abort function are shown in the following table:
| TABLE 2 |
|---|
| Return Values of the IBinding::Abort Function. |
[0326] 5.4.2 The IBinding::Suspend Function
[0327] The IBinding::Suspend function suspends the bind operation. The bind operation will be suspended until resumed by a later call to the IBinding::Resume function or canceled by a call to the IBinding::Abort function. After calling IBinding::Suspend the client may still receive some notifications about the bind operation.
[0328] The return values of the illustrated IBinding::Suspend Function are shown in the following table:
| TABLE 3 |
|---|
| IBinding::Suspend Function Return Values |
[0329] 5.4.3 The IBinding::Resume Function
[0330] The IBinding::Resume function resumes a suspended bind operation. The bind operation must have been previously suspended by a call to the IBinding::Suspend function. The return values of the illustrated IBinding::Suspend function are shown in the following table:
| TABLE 4 |
|---|
| Return Values of the IBinding::Resume Function. |
[0331] 5.4.4 The IBinding::SetPriority Function
[0332] The IBinding::SetPriority function establishes the priority for the bind operation according to an input parameter nPriority. The priority values are taken from the Microsoft Corporation's Win32 thread priority APIs (SetThreadPriority and GetThreadPriority). The final priority is determined from values gathered from all clients of the bind operation. The parameter and return values of the illustrated IBinding::SetPriority function are shown in the following table.
| TABLE 5 |
|---|
| IBinding::SetPriority Function Parameters and Return |
| Values. |
[0333] 5.4.5 The IBinding::GetPriority Function
[0334] The IBinding::GetPriority function retrieves the current priority of the bind operation. The priority values are taken from the Win32 thread priority APIs (SetThreadPriority and GetThreadPriority). The parameters and return values of the illustrated function are shown in the following table.
| TABLE 5 |
|---|
| IBinding::GetPriority Function Parameters and Return |
| Values. |
[0335] 5.5 The IBindStatusCallback Interface
[0336] The IBindStatusCallback interface 162 exposes member functions of the bind-status-callback object 166 provided by the client 152. These members functions are called by the asynchronous moniker 150 and binding object 164 to provide notifications to the client 152 relating to the bind operation, e.g., the bind operation's status and progress updates. The asynchronous moniker 150 calls the notification member functions of the IBindStatusCallback in the IMoniker::BindToObject and BindToStorage functions, and the binding object 164 will continue to call the notification member functions in an asynchronous bind operation after the asynchronous moniker returns from the BindToObject or BindToStorage function.
[0337] The asynchronous moniker 150 also calls two member functions, the GetBindInfo and GetPriority functions (described below), to receive additional information for the bind operation from the client 152. In its BindToObject or BindToStorage function, the asynchronous moniker calls the IBindStatusCallback::GetBindInfo function (described below) to check at least the BINDF_ASYNCHRONOUS flag which indicates whether to perform the bind operation asynchronously. The asynchronous moniker 150 also may call the IBindStatusCallback::GetPriority to set the priority of the bind operation. Further, the asynchronous moniker 150 may call the IBindStatusCallback::QueryInterface function to request an interface pointer of a further interface of the client through which the asynchronous moniker can obtain further information or access additional or extended services.
[0338] In the illustrated embodiment, the client 152 provides the bind-status-callback object 166 in association with a specific bind operation. The caller of the member functions exposed through the IBindStatusCallback interface thus need not pass information identifying the specific bind operation.
[0339] The client 152 registers the IBindStatusCallback interface of its bind-status-callback object 166 into the asynchronous bind context by calling the RegisterBindStatusCallback API function described below. Multiple clients can register with this API function for the same bind operation. Further, each client can specify receiving calls to only particular ones of the IBindStatusCallback interface's member functions from the asynchronous moniker 150 and binding object 164 which perform the bind operation. The asynchronous moniker 150, however, may set any arbitrary order and limits on the clients that receive notifications on particular IBindStatusCallback interface member functions. The asynchronous moniker 150 retrieves interface pointers of the IBindStatusCallback interfaces which are registered for a particular bind operation from the asynchronous bind context in its IMoniker::BindToObject or BindToStorage member functions.
[0340] If the asynchronous moniker 150 invokes other monikers as part of the bind operation, the asynchronous moniker may register its own IBindStatusCallback interface (not shown) in the asynchronous bind context to receive notification from the other moniker. The notifications through the IBindStatusCallback interfaces of more than one moniker involved in a bind operation can thus be chained to provide consolidated progress notifications.
[0341] The definition of the IBindStatusCallback interface 162 and related data structures is as follows:
| typedef enum { |
[0342] 5.5.1 The BINDVERB Enumeration
[0343] The BINDVERB enumeration defines values that are passed to the client 152 with the IBindStatusCallback::GetBindInfo function to distinguish different types of bind operations. The illustrated BINDVERB enumeration values are shown in the following table:
| TABLE 6 |
|---|
| BINDVERB Enumeration Values. |
[0344] 5.5.2 The BINDINFOF Enumeration
[0345] The BINDINFOF enumeration defines values that are passed to the client 152 within the IBindStatusCallback::GetBindInfo function to specify additional flags for controlling the bind operation. The values in the illustrated embodiment are shown in the following table.
| TABLE 7 |
|---|
| BINDINFOF Enumeration Values. |
[0346] 5.5.3 The BINDINFO Structure
[0347] The BINDINFO structure is returned to the asynchronous moniker 150 from the asynchronous moniker's call to the IBindStatusCallback::GetBindInfo function. The client 152 of the asynchronous moniker 150 uses this structure to qualify the bind operation. The meaning of this structure generally is specific to the class of the asynchronous moniker 150. The following table summarizes the meaning of the data values in the structure for the illustrated URL moniker class of asynchronous moniker described below.
| TABLE 8 |
|---|
| BINDINFO Structure Members. |
[0348] 5.5.4 The BSCO_OPTION Enumeration
[0349] The BSCO_OPTION enumeration defines values which the client 152 passes into the asynchronous bind context using the RegisterBindStatusCallback API function when registering a callback for a bind operation. The values identify what binding callback notifications the client 152 receives from the asynchronous moniker 150. Clients can specify only the BSCO_ONDATMVAILABLE flag to receive only the data bits of the object 154 being bound. The flags in the illustrated embodiment are shown in the following table.
| TABLE 9 |
|---|
| BSCO_OPTION Enumeration Flags. |
[0350] 5.5.5 The BINDF Enumeration
[0351] The BINDF enumeration defines flags that are returned to the 15 binding object 164 from the client's IBindStatusCallback::OnStartBinding function. The flags identify what type of binding the asynchronous moniker 150 is to perform. The flags in the illustrated embodiment are shown in the following table.
| TABLE 10 |
|---|
| BINDF Enumeration Flags. |
[0352] 5.5.6 The BSCF Enumeration
[0353] The BSCF enumeration defines flags that are passed to the client 152 by the asynchronous moniker 150 in a call to the client's IBindStatusCallback::OnDataAvailable function to clarify the type of data which is available. The flags in the illustrated embodiment are shown in the following table.
| TABLE 11 |
|---|
| BSCF Enumeration Flags. |
[0354] 5.5.7 The BINDSTATUS Enumeration
[0355] The asynchronous moniker 150 passes a single status value from the BINDSTATUS enumeration as the uIStatusCode parameter to the IBindStatusCallback::OnProgress function to inform the client 152 about the progress of the bind operation. The status values in the illustrated embodiment are shown in the following table.
| TABLE 12 |
|---|
| BINDSTATUS Enumeration Status Values. |
[0356] 5.5.8 The IBindStatusCallback::QueryInterface Function
[0357] The asynchronous moniker 150 calls the IBindStatusCallback::QueryInterface function to query the client 152 for access to an interface which exposes additional services necessary for completing the bind operation. This function provides extensibility to the IBindStatusCallback interface, because it allows querying the client for new interfaces for passing information or querying information. The IEnumFormatEtc interface of URL monikers described below is an example of additional client services that can be made available through this function. The parameters and return values of the illustrated function are shown in the following table.
| TABLE 13 |
|---|
| IBindStatusCallback::QueryInterface Parameters and |
| Return Values. |
[0358] 5.5.9 The IBindStatusCallback::GetBindInfo Function
[0359] The asynchronous moniker 150 calls the IBindStatusCallback::GetBindInfo function to obtain information from the client 152 pertaining to the bind operation. The asynchronous moniker 150 calls this method within its implementations of the IMoniker::BindToObject and BindToStorage functions before returning. The parameters and return values of the illustrated function are shown in the following table.
| TABLE 14 |
|---|
| IBindStatusCallback::GetBindInfo Parameters and Return |
| Values. |
[0360] 5.5.10 The IBindStatusCallback::OnStartBinding Function
[0361] The asynchronous moniker 150 also calls the IBindStatusCallback::OnStartBindingfunction while initiating the bind operation within its implementation of the IMoniker::BindToStorage or IMoniker::BindToObject functions. In this call, the asynchronous moniker 150 notifies the client 152 which of the IBindStatusCallback function the client is registered to receive in response to the callback function notification flags the client requested when registering its IBindStatusCallback interface with the asynchronous bind context using the RegisterBindStatusCallback API function described below.
[0362] In its call to this function, the asynchronous moniker 150 also passes an interface pointer of the IBinding interface 160 of the binding object 164 associated with the current bind operation to the client 152. As detailed above, the IBinding interface 160 allows the client 152 to exert control over the bind operation by calling the member functions on the IBinding interface of the binding object. The client's bind-status-callback object 166 stores the IBinding interface pointer and maintains accurate reference counting by calling the standard OLE AddRef and Release functions on the IBinding interface in accordance with OLE conventions.
[0363] The parameters and return values of the illustrated IBindStatusCallback::OnStartBinding function are shown in the following table.
| TABLE 15 |
|---|
| IBindStatusCallback::OnStartBinding Parameters and |
| Return Values. |
[0364] 5.5.11 The IBindStatusCallback::GetPriority Function
[0365] Typically, the asynchronous moniker 150 calls the IBindStatusCallback::GetPriority function to obtain the priority of the bind operation prior to initiating asynchronous binding by the binding object 164. Additionally, the function may be called at any time during the bind operation if the asynchronous moniker 150 needs to make new priority decisions. The asynchronous moniker 150 can use the priority to set the actual priority of a thread associated with a download operation (i.e., the thread executing the binding object 164), but more commonly the asynchronous moniker interprets the priority to perform its own scheduling among multiple bind operations. The parameter and return values of the illustrated function are shown in the following table.
| TABLE 16 |
|---|
| IBindStatusCallback::GetPriority Parameters and Return |
| Values. |
[0366] 5.5.12 The IBindStatusCallback::OnProgress Function
[0367] The binding object 164 calls the IBindStatusCallback::OnProgress function repeatedly to indicate the current progress of the bind operation, preferably at reasonable intervals during a lengthy bind operation. The client 152 may use the progress notification to provide progress information to the user, such as by displaying a “% complete” bar graph, a download status notification message or like progress indicating user interface control. The client 152 also may use the progress notification to make programmatic decisions based on the uIStatusCode parameter. The parameters and return values of the illustrated function are shown in the following table.
| TABLE 17 |
|---|
| IBindStatusCallback::OnProgress Parameters and Return |
| Values. |
[0368] 5.5.13 The IBindStatusCallback::OnDataAvailable Function
[0369] During asynchronous binding using the asynchronous moniker's IMoniker::BindToStorage function, the asynchronous moniker 150 calls the IBindStatusCallback::OnDataAvailable function to provide data to the client 152 as it becomes available. As described above, the behavior of the storage passed to the client 152 by the asynchronous moniker 150 in the pstgmed parameter depends on the BINDF flags that the client returned from the IBindStatusCallback::GetBindInfo function. More particularly, the storage may be asynchronous or blocking. Further, the bind operation may follow a “data pull” model or a “data push” model. For the data pull model, the client is not able to seek backwards in the data stream provided by the asynchronous moniker in the IBindStatusCallback::OnDataAvailable call. On the other hand, for push model bind operations, the client 152 commonly can seek back into a data stream and read any data that has been downloaded for an ongoing IMoniker::BindToStorage operation.
[0370] The parameters and return values of the illustrated IBindStatusCallback::OnDataAvailable function are shown in the following table.
| TABLE 18 |
|---|
| Parameters and Return Values of the |
| IBindStatusCallback::OnDataAvailable Function. |
[0371] 5.5.14 The IBindStatusCallback::OnObiectAvailable Function
[0372] During asynchronous binding using the asynchronous moniker's IMoniker::BindToObject function, the asynchronous moniker 150 calls the IBindStatusCallback::OnObjectAvailable function to pass the requested object interface pointer to the client 152. The asynchronous moniker 150 never calls this function for asynchronous binding performed using the IMoniker::BindToStorage function. The parameters and return values of the illustrated IBindStatusCallback:;OnObjectAvailable function are shown in the following table.
| TABLE 19 |
|---|
| Parameters and Return Values of the |
| IBindStatusCallback::OnObjectAvailable Function. |
[0373] 5.5.15 The IBindStatusCallback::OnLowResource Function
[0374] The asynchronous moniker 150 calls this function when it detects low resources. The client 152 should free any resource it no longer needs when receiving this notification. The illustrated function's parameters and return values are shown in the following table.
| TABLE 20 |
|---|
| IBindStatusCallback::OnLowResource Parameters and |
| Return Values. |
[0375] 5.5.16 The IBindStatusCallback::OnStopBinding Function
[0376] The asynchronous moniker 150 calls IBindStatusCallback::OnStopBinding function to indicate the end of the bind operation. This function is always called, whether the bind operation succeeded, failed, or was aborted by the client 152. When this function is called, the client 152 must call the Release function on the IBinding interface pointer it received in the asynchronous moniker's call to the IBindStatusCallback::OnStartBinding function. The parameters and return values of the illustrated IBindStatusCallback::OnStopBinding function are shown in the following table.
| TABLE 21 |
|---|
| IBindStatusCallback::OnStopBinding function |
[0377] 5.6 The IPersistMoniker Interface
[0378] The object 154 which is named by the asynchronous moniker can support an IPersistMoniker interface 170 to obtain more control over the way the object is bound to its persistent data. When instantiating and initializing the named object 154 in the IMoniker::BindToObject function, the asynchronous moniker 150 queries the named object for persistence interfaces, such as the IPersistMoniker Interface 170 or the standard OLE IPersistFile, IPersistStream[Init], or IPersistStorage interfaces, which the asynchronous moniker then utilizes in the bind operation to load the object's persistent data. In the illustrated embodiment, the asynchronous moniker 150 uses the highest precedence interface supported by the object in the following order: IPersistMoniker, IPersistStream[Init], IPersistStorage, IPersistFile, IPersistMemory.
[0379] The IPersistMoniker interface 170 allows monikers and other application programs which instantiate objects from persistent data to give control to the object 154 to choose how the object is bound to its persistent data. The object 154 can implement a IPersistMoniker::Load function (described below) with code that calls IMoniker::BindToStorage on a moniker that names the object's persistent state and specifies a preferred interface and binding options, such as IStorage, IStream, asynchronously bound, etc.
[0380] 5.6.1 The IPersistMoniker::IsDirty Function
[0381] The IPersistMoniker::IsDirty function checks whether the persistent state of the object has changed since it was last saved. The illustrated function's return values are shown in the following table.
| TABLE 22 |
|---|
| IPersistMoniker::IsDirty Return Values. |
[0382] 5.6.2 The IPersistMoniker::Load Function
[0383] The IPersistMoniker::Load function loads the object with its persistent state referred to by a parameter, pmkSrc. The implementation of the IPersistMoniker::Load function in the illustrated object immediately binds to its persistent state with the call, pmkSrc->BindToStorage(pbc, . . . ), specifying either IStream or IStorage as the interface pointer parameter of the call. The following table summarizes the parameters and return values of the illustrated IPersistMoniker::Load function.
| TABLE 23 |
|---|
| IPersistMoniker::Load Parameters and Return Values. |
[0384] 5.6.3 The IPersistMoniker::Save Function
[0385] The IPersistMoniker::Save function is called to request that the object 154 save itself into the location referred to by the moniker pointer parameter, pmkDst. The illustrated function's parameters and return values are shown in the following table.
| TABLE 24 |
|---|
| IPersistMoniker::Save Parameters and Return Values |
[0386] 5.6.4 The IPersistMoniker::SaveCompleted
[0387] Calling this function notifies the object that it has been completely saved and points the object to its new persisted state. The implementation of this function in the illustrated object 154 immediately bind to the object's persistent state using the code, pmkNew->BindToStorage(pbc, . . . ), and specifying either IStream or IStorage, as in the implementation of IPersistMoniker::Load function. The parameters and return values of the illustrated IPersistMoniker::SaveCompleted function are shown in the following table.
| TABLE 25 |
|---|
| IPersistMoniker::SaveCompleted Parameters and Return |
| Values. |
[0388] 5.6.5 The IPersistMoniker::GetCurMoniker Function
[0389] This function is used to retrieve the moniker that refers to the object's persistent state. Typically, this is the moniker last passed to the object via IPersistMoniker::Load, IPersistMoniker::Save or IPersistMoniker::SaveCompleted. The parameter and return values of the illustrated IPersistMoniker::GetCurMoniker function are shown in the following table.
| TABLE 26 |
|---|
| IPersistMoniker::GetCurMoniker Parameter and Return |
| Value. |
[0390] 5.7 API Functions for Asynchronous Monikers
[0391] For use in asynchronous binding using the asynchronous moniker 150, the system 158 provides several API functions described below.
[0392] 5.7.1 The CreateAsyncBindCtx API Function
[0393] The system 158 provides a CreateAsyncBindCtx API function having the following form:
[0394] HRESULT CreateAsyncBindCtx(dwReserved, pbsc, grfBSCOption, penumfmtetc, ppbc);
[0395] The client 152 calls the CreateAsyncBindCtx API function to create an asynchronous bind context for use with the asynchronous moniker 150. The CreateAsyncBindCtx API function automatically registers the IBindStatusCallback interface 162 and the IEnumFORMATETC interface (described below) with the asynchronous bind context. The grfBSCOption parameter allows the client 152 to specify flags that determine which of the IBindStatusCallback interface's notification functions the client is capable of receiving. The client 152 can implement some notification callback functions that it does not use as empty function stubs (which return the E_NOTIMPL value). The client 152 then specifies not to receive notifications to the unimplemented IBindStatusCallback functions in the bind context registration. As a result, the asynchronous moniker 150 will not call those functions during asynchronous binding.
[0396] The parameters and return values of the illustrated CreateAsyncBindCtx API function are shown in the following table.
| TABLE 27 |
|---|
| CreateAsyncBindCtx API Function Parameters and Return |
| Values. |
[0397] 5.7.2 The RegisterBindStatusCallback API Function
[0398] The system 158 provides a RegisterBindStatusCallback API function having the following form.
[0399] HRESULT RegisterBindStatusCallback(pbc, pbsc, grfBSCOption, dwReserved);
[0400] The client 152 call the RegisterBindStatusCallback API function to register its IBindStatusCallback interface with an existing bind context. The RegisterBindStatusCallback API function also allows the client to specify flags that determine which callback notifications the client is capable of receiving. The client may implement functions for callback notifications that it does not receive as empty function stubs (returning E_NOTIMPL).
[0401] This API function allows multiple clients to each register a callback for the same bind context. During the bind operation, these callbacks are called in an arbitrary order, and the asynchronous moniker may set policy and limit certain callback notifications (e.g. GetBindInfo, OnDataAvailable, OnObjectAvailable) to only one of the registered callbacks. For this reason, the client 152 should request to receive only those callback notifications that it implements.
[0402] The parameters and return values of the RegisterBindStatusCallback API function in the illustrated embodiment are shown in the following table.
| TABLE 28 |
|---|
| RegisterBindStatusCallback API FunctionParameters and |
| Return Values. |
[0403] 5.7.3 The RevokeBindStatusCallback API Function
[0404] The system 158 provides a RevokeBindStatusCallback API function having the following form.
[0405] HRESULT RevokeBindStatusCallback( );
[0406] The client 152 calls the RevokeBindStatusCallback API function to revoke a previous IBindStatusCallback interface registration in the asynchronous bind context. This call will not succeed if it is made during a bind operation.
| TABLE 29 |
|---|
| RevokeBindStatusCallback API Function Parameters and |
| Return Values. |
[0407] 5.7.4 The IsAsyncMoniker API Function
[0408] The system 158 provides an IsAsyncMoniker API function having the following form.
[0409] HRESULT IsAsyncMoniker(pmk);
[0410] By calling this API, the client 152 tests whether a moniker supports asynchronous binding. The illustrated asynchronous moniker 150 implementation indicates that it is asynchronous by supporting an IMonikerAsync interface, an “empty” interface which is actually just IUnknown, having the following form.
| MyCustomMoniker::QueryInterface(REFIID riid, void** ppv) { | |
| if (riid == IID_IUnknown ||riid == IID_IPersistStream||riid | |
| = ID_IMoniker||riid == IID_IAsyncMoniker) { | |
| *ppv = this; | |
| Add Ref(); | |
| return S_OK; | |
| } | |
| *ppv = NULL; | |
| return E_NOINTERFACE; | |
| } | |
[0411] The implementation of the IsAsyncMoniker API function tests support for this interface by the moniker to determine if it is asynchronous. The parameter and return values of the illustrated IsAsyncMoniker API function are shown in the following table.
| TABLE 30 |
|---|
| IsAsyncMoniker API Function Parameter and Return Values. |
[0412] 6. URL Monikers
[0413] According to the illustrated embodiment of the invention shown in FIG. 7, a client program (hereafter “client”) 202 utilizes an URL moniker 200 provided by an operating system component (hereafter “system”) 204 (specifically a component such as the COM library 114 which also implements the API functions described above for asynchronous monikers and the API functions described below for URL monikers) to asynchronously bind to an object 208 named by an uniform resource locator (URL). URLs are a well known encoding of names and addresses of resources (e.g., documents, images, and other data) residing on the Internet. URLs generally comprise a transport protocol identifier (e.g., “http,” “ftp,” “gopher,” etc.), a site name (e.g., “www.microsoft.com”), and a resource name (e.g., “document.html”), such as the following text string example: “http://www.microsoft.com/intdev/page.html.” URLs are described in more detail in the following documents currently available from the Internet: Uniform Resource Locators(URL), http://ds.internic.net/rfc/rfc1738.txt; Relative Uniform Resource Locators,http://ds.internic.net/rfc/rfc11808.txt; Universal Resource Identifiers in WWW(RFC1630), http://ds.internic.net/rfc/rfc1630.txt; Names and Addresses, URIs, URLs, URNs, URCs,http://www.w3.org/pub/WWW/Addressing/Addressing.html; and IETF—Hypertext Transfer Protocol(HTTP) Working Group,http://www.ics. uci.edu/pub/ietf/http.
[0414] The URL moniker 200 is an instance of a class derived from the asynchronous moniker class, and supports the IMoniker interface 124. Since the IMoniker interface 124 is derived from the IPersistStream interface, the URL moniker 200 also supports the IPersistStream, IPersist, and IUnknown interfaces (which are standard OLE interfaces). Also, as described above for the asynchronous moniker 150, the URL moniker 200 supports the IAsyncMoniker interface which is a stub interface that is used to allow the client 202 to determine whether the moniker supports asynchronous binding (which the URL moniker does).
[0415] In an asynchronous bind operation, the URL moniker 200 makes use of a transport object 210 which supports the IBinding interface 152 and implements an Internet transport protocol (e.g., HTTP, FTP, or Gopher) associated with the URL of the URL moniker. The illustrated transport object 210 is provided by the system 204, and additionally supports an IBindProtocol interface 212 (described more fully below), the IParseDisplayName interface (described above), and protocol specific interfaces 214 which may be required for interacting with other operating system components involved in downloading data from the Internet (e.g., the “WinSock” or “WinInet” layer of the Windows® 95 operating system).
[0416] To support asynchronous binding, the client 202 implements the bind-status-callback object 166 which supports the IBindStatusCallback interface 162, and registers the IBindStatusCallback interface 162 with the asynchronous bind context 156. The illustrated client 202 additionally implements a format enumerator object 220 which supports an IEnumFORMATETC interface 222 for media-type negotiation (described more fully below). The client 202 also registers the IEnumFORMATETC interface 222 with the asynchronous bind context 156.
[0417] The client 202 makes use of the URL moniker 200 in a way generally similar to the use of the asynchronous moniker 150 described above. The client 202 creates the asynchronous bind context 156 with a call to the CreateAsyncBindCtx API function (described above) of the system component 204, and registers the IBindStatusCallback interface 162 of its bind-status-callback object 166 in the asynchronous bind context 156 with flags specifying which callback notifications the bind-status-callback object receives from the URL moniker. The client 202 also creates the URL moniker 200, such as by calling the CreateURLMoniker API function (described below) or the MkParseDisplayName API function of the system 204. From creating the asynchronous bind context 156 and the URL moniker 200, the client 202 obtains pointers to the IBindCtx interface 128 and the IMoniker interface 124 which the client stores as pbc and pmk pointer variables 134, 136. The client 202 then calls the IMoniker::BindToObject or IMoniker::BindToStorage functions of the URL moniker and passes an interface pointer of the IBindCtx interface 128 of the asynchronous bind context 156 to the URL moniker 200 to initiate binding to the object named by the URL moniker 200.
[0418] In the URL moniker's IMoniker::BindToObject or BindToStorage function, the URL moniker 200 identifies the Internet protocol associated with the URL according to the transport prefix of the URL, and retrieves the IBinding interface 160 of the transport object 210 which implements the associated Internet protocol. The URL moniker 200 also looks up the IBindStatusCallback interface 162 of the bind-status-callback object 166 registered by the client 202 in the asynchronous bind context 156. The URL moniker 200 then passes an interface pointer of the IBinding interface 160 to the bind-status-callback object 166 in a call to the OnStartBinding function on the IBindStatusCallback interface 162. As described above, the client calls functions on the IBinding interface 160 to effect pausing, cancellation, and prioritization of the asynchronous binding operation.
[0419] The URL moniker 200 also passes its pointer for the IBindStatusCallback interface 162 to the transport object 210 when initiating the bind operation. During the bind operation, the transport object 210 calls notification functions on the IBindStatusCallback interface 162. In particular, the bind-status-callback object 166 receives progress notification through the IBindStatusCallback::OnProgress function, data availability notification through the IBindStatusCallback::OnDataAvailable function, as well as various other notifications from the transport object 210 about the status of the bind operation.
[0420] The URL moniker 200 or transport object 210 may also request extended information from the client 202 via the IBindStatusCallback::QueryInterface function, allowing the client 202 to provide protocol-specific information that will affect the bind operation.
[0421] 6.1 Media-type Negotiation with the URL Moniker
[0422] The URL moniker 200 supports media type negotiation in order to allow clients to negotiate the format of the named object's data to be downloaded in the URL's BindToStorage function (i.e., where the URL moniker downloads the named object's data directly into the computer's secondary storage 42 (FIG. 1), rather than loading the data into the running object 208). The client 202 requests preferred data format(s) using the IEnumFORMATETC interface 222 on the format enumerator object 220. The client 202 creates the format enumerator object 220, and registers the IEnumFORMATETC interface 222 with the asynchronous bind context 156. The client registers the IEnumFORMATETC interface 222 in a call to the CreateAsyncBindCtx API function (described above), or with the RegisterFormatEnumerator API function (described below) as shown in the following example code:
[0423] CreateBindCtx(0, &pbc);
[0424] RegisterFormatEnumerator(pbc, &enumfmtetc, 0);
[0425] The URL moniker 200 obtains an interface pointer to the IEnumFORMATETC interface 222 from the asynchronous bind context 156 when performing a bind operation in the IMoniker::BindToStorage or BindToObject functions. The URL moniker 200 then calls functions on the IEnumFORMATETC interface 222 to obtain the client's preferred data format(s). The client 202 represents the requested preferred format(s) to the URL moniker 200 through FORMATETC data structures (described below) in the format enumerator object 220 which the client makes available from the IEnumFORMATETC interface 222.
[0426] Each FORMATETC data structure specifies a clipboard format value identifying a preferred data format (media type), a “NULL” target device value, a “DVASPECT_CONTENT” value, a “lindex” value of −1, and a “TYMED_NULL” value. The clipboard format values are value used by the well known OLE Clipboard protocol for exchanging data between two programs, such as in cut/copy/paste or drag-and-drop operations between programs. An example of code for creating a FORMATETC data structure in the client 202 follows:
[0427] FORMATETC fmtetc;
[0428] fmtetc.cfFormat=
[0429] RegisterClipboardFormat(CF—MIME_POSTSCRIPT);
[0430] fmtetc.ptd=NULL;
[0431] fmtetc.dwAspect=DVASPECT_CONTENT;
[0432] fmtetc.lindex=−1;
[0433] fmtetc.tymed=TYMED_NULL;
[0434] A special clipboard format value, “CF_NULL”, can be used by the client 202 in a FORMATETC data structure to indicate that the default media type of the resource pointed to by the URL should be retrieved. Although the FORMATETC data structure with the CF_NULL clipboard format value can be placed anywhere within the enumerator, the client 202 generally lists such a FORMATETC data structure as last in order of priority of the client's preferred data formats.
[0435] When no FORMATETC enumerator 220 is registered with the asynchronous bind context 156 (which is a common case), the URL moniker 200 operates as if an enumerator containing a single FORMATETC with a clipboard format value equal to CF_NULL is available. More specifically, the URL moniker 200 will automatically bind to or download the default media-type of the resource named by the URL.
[0436] When performing a bind operation for the client 202, the URL moniker 200 translates the preferred data format(s) specified in the FORMATETC data structures into Multipurpose Internet Mail Extension (MIME) media types. MIME is a well known protocol for electronic mail exchange on the Internet. Many application-level Internet protocols are based on the exchange of messages using MIME media types. MIME was originally developed for exchanging electronic mail messages with rich content across heterogeneous networking, machine, and e-mail environments. MIME has since been adopted in numerous non-mail applications, and several of its useful core features extended by further protocols, such as Hyper-Text Transfer Protocol(HTTP) used on the world wide web. Further details of MIME and its use in HTTP are described in the following documents available from the Internet: MIME Overview,http://ds.internic.net/rfc/rfc1630.txt; Media Type Registration Procedure,http://ds.internic.net/rfc/rfc1590.txt; and IETF—Hypertext Transfer Protocol(HTTP) Working Group,http://www.ics.uci.edu/pub/ietf/http.
[0437] The URL moniker 200 uses the MIME media types to request downloading the data named by the URL using the highest priority of the client's preferred data formats in which the data is available from its site on the Internet. MIME media types are simple strings which denote a type and subtype (such as “text/plain” or “text/html”) and are used to label data or qualify a request. In general, the URL moniker 200 lists media types in the client's priority order, and the Internet server (or world wide web site) where the data resides responds with the highest priority available data format. For example, when the URL moniker is binding to a URL of an image which specifies the HTTP protocol, the transport object 210 lists as part of an HTTP request-for-data (Get Request-Line) or request-for-info (Head Request-Line) that it is requesting “image/gif” or “image/jpeg” MIME media types. If the data is available in the image/gif data format, the world wide web site for the URL responds by returning the MIME media type of “image/gif” and optionally the image data itself in the GIF format if the call was a request-for-data.
[0438] The client 202 is notified of the actual data format that it receives during the bind operation of the BindToStorage function through the pformatetc argument on the client's IBindStatusCallback::OnDataAvailable function.
[0439] 6.1.1 The RegisterMediaTypes API Function
[0440] This API function registers text strings of MIME media types with corresponding clipboard format values for use in clipboard format value to MIME media type mapping by the URL moniker 200 in media type negotiation for the client 202. The RegisterMediaTypes API function has the following form:
[0441] HRESULT RegisterMediaTypes(ctypes, rgszTypes, rgcfTypes);
[0442] The parameters and return values of the RegisterMediaTypes API function are shown in the following table.
| TABLE 31 |
|---|
| RegisterMediaTypes API Function Parameters and Return Values. |
[0443] 6.1.2 The CreateFormatEnumerator API Function
[0444] This function creates an object which implements the IEnumFORMATETC interface over a static array of FORMATETC data structures. The client 202 can call this API function to create the format enumerator object 220 for use in media type negotiation with the URL moniker 200. The CreateFormatEnumerator API function has the following form:
[0445] HRESULT CreateFormatEnumerator(cfmtetc, rgfmtetc, ppenumfmtetc);
[0446] The parameters and return values of the CreateFormatEnumerator API function are shown in the following table.
| TABLE 32 |
|---|
| CreateFormatEnumerator API Function Parameters and Return Values. |
[0447] 6.1.3 The RegisterFormatEnumerator API Function
[0448] The client 202 calls this API function to register the format enumerator object 220 onto the bind context 156. This allows the URL moniker 200 to query for the client's preferred data formats for media type negotiation in a subsequent bind operation as described above. The RegisterFormatEnumerator API function has the following form:
[0449] HRESULT RegisterFormatEnumerator(pbc, pEFetc, dwReserved);
[0450] The parameters and return value of the RegisterFormatEnumerator API function are shown in the following table.
| TABLE 33 |
|---|
| RegisterFormatEnumerator API Function Parameters |
| and Return Values. |
[0451] 6.1.4 The RevokeFormatEnumerator API Function
[0452] The client 202 calls this API function to removes the format enumerator object 220 from registration with the asynchronous bind context 156. The API function has the following form:
[0453] HRESULT RevokeFormatEnumerator(pbc, pEFetc);
[0454] The parameters and return values of the RevokeFormatEnumerator API function are shown in the following table.
| TABLE 34 |
|---|
| RevokeFormatEnumerator API Function Parameters |
| and Return Values. |
[0455] 6.1.5 The CreateURLMoniker API Function
[0456] The client 202 calls this function to create the URL moniker 200 from a given URL. The function also can be called from a ParseDisplayName function called through the IParseDisplayName interface described above. The CreateURLMoniker API function has the following form:
[0457] HRESULT CreateURLMoniker(pmkContext, szURL, ppmk);
[0458] The CreateURLMoniker API function creates the URL moniker 200 from either a full URL string or from a partial URL string. The partial URL string identifies a resource on the Internet relative to a base context. The full URL string identifies a resource independent of any context. The caller can create the URL moniker to name a partial URL string by specifying a separate URL moniker that names the base context as the pmkContext parameter. In this case, the CreateURLMoniker API function retrieves the display name of the base context URL moniker by calling the IMoniker::GetDisplayName function on the base context URL moniker, and then manually composes the base context together with the partial URL string specified in the szURL parameter according to URL composition rules.
[0459] The caller alternatively can create the URL moniker 200 from a partial URL string without specifying the base context (i.e., with pmkContext=NULL). In such case, the URL moniker 200 will draw further context during binding (i.e., in the IMoniker::BindToObject and IMoniker::BindToStorage functions) from the asynchronous bind context 156. The URL moniker 200 obtains the base context by looking for a contextual URL moniker parameter held by the asynchronous bind context 156, such with the function call, IBindCtx::GetObjectParam(SZ_URLCONTEXT, (IUNKNOWN**)&pmkContext). The base context can be contained as a set of URL monikers which form a compound moniker (a well known type of OLE moniker), in which case the URL moniker 200 continues looking at each URL moniker to the left of the first URL moniker obtained from the IBindCtx::GetObjectParam function call to complete the base context.
[0460] The parameters and return values of the CreateURLMoniker API function are shown in the following table.
| TABLE 35 |
|---|
| CreateURLMoniker API Function Parameters and Return Values. |
[0461] 6.2 URL Moniker Functions
[0462] The implementation of the member functions of the URL moniker 200 is described in further detail below. These functions have the form defined for the member functions of the IUNKNOWN, IAsyncMoniker, IPersist, IPersistStream, and IMoniker interfaces which are described above or are well known OLE interfaces described in Inside Ole, Second Edition,supra.
[0463] 6.2.1 The URL Moniker-IUNKNOWN::QueryInterface Function
[0464] The client 202 uses this function to request an interface pointer of another of the OLE moniker's interfaces. The URL Moniker 200 supports the interfaces, IUNKNOWN, IASYNCMONIKER, IPersist, IPersistStream, and IMoniker. As described above, the IAsyncMoniker interface is a stub interface having no member functions that is used to allow the client 202 to determine transparently if the URL moniker 200 supports asynchronous binding. This function has the form of the standard OLE IUNKNOWN::QueryInterface function.
[0465] 6.2.2 The URL Moniker-IPersist::GetClassID Function
[0466] This function returns the class identifier of the URL moniker's class, CLSID_StdURLMoniker. This function has the form of the standard OLE IPersist::GetClassID function.
[0467] 6.2.3 The URL Moniker-IPersistStream::IsDirty Function
[0468] The client 202 calls this function to check whether the URL held by the URL moniker 200 has changed since the URL moniker was last saved to the computer's secondary storage 42 (FIG. 1). The implementation of this function in the URL moniker 200 returns the value, S_OK, if the URL Moniker 200 has changed since it was last saved (i.e., with a call to the IPersistStream::Save function described below, with the parameter fClearDirty==TRUE). Otherwise, the function returns the value, S_FALSE. This function has the form of the standard OLE IPersistStream::IsDirty function.
[0469] 6.2.4 The URL Moniker-IPersistStream::Load Function
[0470] This function initializes the URL moniker 200 from data (a URL string) stored within a stream. The stream usually is stored previously using the URL moniker's IPersistStream::Save function described below (via OleSaveToStream or OleSaveToStreamEx). The binary format of the stream is the URL string in Unicode™, which is a well known fixed width 16-bit encoding standard of international character sets. The URL string may be a full or partial URL string as described above in connection with the CreateURLMoniker API function. The URL string is represented as a ULONG (32-bit) data type value indicating a count of characters followed by that many Unicode characters. This function has the form of the standard OLE IPersistStream::Load function.
[0471] 6.2.5 The URL Moniker-IPersistStream::Save Function
[0472] This function saves the URL named by the URL moniker 200 to a data stream in the computer's secondary storage 42 (FIG. 1). The function saves the URL in a binary format comprising a ULONG (32-bit) data type value indicating a count of characters in the URL followed by that many Unicode™ characters. As described above, the URL may be a full or partial URL string. This function has the form of the standard OLE IPersistStream::Save function.
[0473] 6.2.6 The URL Moniker-IPersistStream::GetSizeMax Function
[0474] This function returns the maximum number of bytes in the data stream in which a subsequent call to the IPersistStream::Save function stores the URL of the URL moniker 200. The function computes the maximum bytes value as SIZEOF(ULONG)==4 plus SIZEOF(WCHAR)*n, where n is the length of the full or partial URL string including the NULL terminator character. The function has the form of the standard OLE IPersistStream::GetSizeMax function.
[0475] 6.2.7 The URL Moniker-IMoniker::BindToObject Function
[0476] This function has the form of the standard OLE IMoniker::BindToObject function, and implements the URL moniker's binding process which instantiates the named object 208 as a running object in the computer's main memory 40 (FIG. 1). In the same manner as the asynchronous moniker 150 described above, the URL moniker 200 supports asynchronous and synchronous binding as determined by the client setting the BINDF_ASYNCHRONOUS flag passed in response to the URL moniker's IBindStatusCallback::GetBindInfo function call.
[0477] FIGS. 8A-8B show the asynchronous binding process 250 implemented in the IMoniker::BindToObject function of the URL moniker 200 (which the URL moniker performs when the BINDF_ASYNCHRONOUS flag is set). At a first step 252, the URL moniker 200 gets information for use in the bind operation from the asynchronous bind context 156, including particularly pointers for the IBindStatusCallback interface 166 and the IEnumFORMATETC interface 222 which are registered by the client 202 in the asynchronous bind context.
[0478] In a next step 253, the URL moniker 200 checks the running object table of the asynchronous bind context 156 to determine if the object 208 named by the URL moniker is already running, such as with the following code statements:
[0479] IBindCtx::GetRunningObjectTable(&prot);
[0480] prot->IsRunning(this);
[0481] If the named object 208 is already running, the URL moniker 200 retrieves the running named object 208 at step 254 (such as with the code statement: prot->GetObject(this, &punk)), and continues to step 270 of FIG. 8B.
[0482] Otherwise, the URL moniker 200 proceeds to query the client 202 for bind information by calling the IBindStatusCallback::GetBindInfo function at step 256. In this bind information, the client 202 indicates that the bind operation is to be performed asynchronously by setting the BINDF_ASYNCHRONOUS flag. At step 257, the URL moniker 200 then initiates the bind operation with the transport object 210 according to the bind information specified by the client. The URL moniker 200 selects the transport object which implements the transport protocol specified in the URL prefix (e.g., an HTTP transport object for an URL with the prefix, “http:\\”). The transport object 210 begins retrieving the resource designated by the URL, such as by connecting to the URL's site on the Internet, and requesting the resource. The illustrated transport object 210 retrieves the resource to a stream object which supports the standard OLE interface, IStream.
[0483] The URL moniker 200 also passes an interface pointer of the transport object's IBinding interface to the client 202 at step 258 via the client's IBindStatusCallback::OnStartBinding function. Finally at step 259, the IMoniker::BindToObject function of the URL moniker 200 returns the value, MK_S_ASYNCHRONOUS, to the client 202, with NULL as the ppv output parameter. The remaining steps 260-271 of FIG. 8B are executed asynchronously (i.e., without blocking the client's execution) in the URL moniker's transport object 210.
[0484] At step 260, the class (i.e., CLSID) associated with the resource designated by the URL Moniker 200 is determined in one of several ways. In the case of the HTTP transport protocol, the initial HTTP response packet header that the transport object 210 receives when requesting the resource from its Internet site may contain the CLSID associated with the resource as an “Extension-Header” to the “Entity Header” section of the “Full-Response” message. The CLSID in the HTTP response packet header is a character string having the following form:
[0485] CLSID=“CLSID” “;” stringized-clsid
[0486] where stringized-clsid is a character string created using the StringFromCLSID API function. The transport object 210 interprets the stringized-clsid using the CLSIDFromString API function. The StringFromCLSID and CLSIDFromString API functions are well known OLE API functions. The extension header of the HTTP response packet is described in more detail in the following documents available from the Internet: Hypertext Transfer Protocol—HTTP1.0, http://www.ics.uci.edu/pub/ietf/http/draft-ietf-http-v10-spec-04.html; IETF—Hypertext Transfer Protocol(HTTP) Working Group,http://www.ics.uci.edu/pub/ietf/http
[0487] The URL moniker 200 also can determine the class associated with the URL by examining the MIME media type of the resource. If the resource has the media type, “application/x-oleobject,” then the first 16-bytes of the resource's actual (i.e., non-header) data (termed the “Content-Body”) contain the CLSID associated with the resource, and subsequent data of the Content-Body is to be interpreted by the class identified by the CLSID. For all other media types, the URL moniker 200 looks in the system registry for the key, HKEY_CLASSES_ROOT\MIME\Database\Content-Type\<media-type>\CLSID, where <media-type> is the resource's media type and “CLSID” is the CLSID associated with that media type.
[0488] The URL moniker 200 can further determine the CLSID of the URL designated resource's class by matching portions of arriving data to patterns registered in the system registry under the keys, HKEY_CLASSES_ROOT\FileTypes, as is well known in OLE and used in the GetClassFile API function.
[0489] Finally, if the above techniques fail, the URL moniker correlates the trailing extension of the resource's name (e.g., “.gif,” “.html,” “.doc,” “.vsd,” etc.), if any, to a CLSID using the HKEY_CLASSES_ROOT\.xxx keys in the system registry, as is also well known in OLE and used in the GetClassFile API function and by the Windows® operating system shell program.
[0490] Next, at step 261, the URL moniker 200 creates the named object 208 based on the resource's CLSID using the CoCreateinstance API function, and requesting the IUNKNOWN interface. The URL Moniker 200 then calls the QueryInterface function on the IUNKNOWN interface of the object 208 to obtain the highest level IPersistxxx interface supported by the object (i.e., in the order IPersistMoniker, IPersistStream, and IPersistFile) as shown at steps 262, 263, 266 and 268.
[0491] If the object 208 supports the IPersistMoniker interface 170, the URL moniker calls the objects's IPersistMoniker::Load function and specifies itself as that function's moniker parameter (e.g., by passing the pointer, “this,” as the parameter) at step 264. The object 208, in turn, typically calls the URL moniker's IMoniker::BindToStorage at step 265, and specifies the object's preferred IPersistxxx interface in the call.
[0492] Otherwise, if the object 208 supports the IPersistStream interface, the URL moniker calls the object's IPersistStream::Load function, and passes as a parameter of the call the IStream object which is being filled with the data of the resource that the transport object 210 is downloading asynchronously from the Internet. This causes the object 208 to load its state from the resource that the transport object is asynchronously downloading. If the object 208 is of an asynchronously aware class (i.e., the CLSID of the object's class is marked in the system registry with the category CATID_AsyncAware), the object can access the resource's data from the IStream as it is downloaded by the transport object 210 from the Internet with the IStream::Read and IStream::Write functions. If the object's class is not in the asynchronously aware category, calls to the IStream::Read or IStream::Write function which reference data that is not yet available block until the data becomes available. If the object's class is marked with the category CATID_AsyncAware, then calls to the IStream::Read or IStream::Write function which reference data not yet available return the value, E_PENDING.
[0493] Finally, if the IPersistFile interface is the highest IPersistxxx interface supported by the object, the URL moniker 200 completes the download of the resource's data into a temporary file. The URL moniker 200 then calls the load function on the object's IPersistFile interface. In the illustrated embodiment, the temporary file is cached along with other Internet-downloaded data, so the client must be sure not to delete the file.
[0494] When the object 208 returns from one of the various IPersistXXX::Load calls above at steps 265, 267 and 269, the URL moniker 200 queries the object using the IUNKNOWN::QueryInterface function at step 270 for an interface pointer that the client 202 originally requested in the client's call to the URL moniker's IMoniker::BindToObject function. Finally, at step 271, the URL moniker 200 returns this interface pointer to the client using the client's IBindStatusCallBack::OnObjectAvailable function.
[0495] 6.2.8 The URL Moniker-IMoniker::BindToStorage Function
[0496] The client 202 calls the BindToStorage function to cause the URL moniker 200 to download the named resource into the secondary storage 42 of the computer 20 (FIG. 1). The implementation of the BindToStorage function in the illustrated URL moniker 200 is similar to the BindToObject function (i.e., having the operation shown in FIGS. 8A and 8B) except that, rather than instantiating the data of the resource designated by the URL moniker as an object of a class associated with the resource (as shown at steps 260-269 of FIG. 8B), the URL moniker provides the resource's data to the client as a storage object. More specifically, in its call to the BindToStorage function, the client 202 can specify the IStream, Istorage, or IUNKNOWN interfaces (which are each well known OLE interfaces described in Inside OLE. Second Edition,supra). If the IStream interface is requested, the URL moniker 200 provides the downloaded data to the client 202 as an object (“IStream object”) which supports the IStream interface. If the IStorage interface is requested and the resource named by the URL moniker is an OLE compound file (a well known OLE file format described in Inside OLE. Second Edition,supra), the URL moniker 200 provides the downloaded data to the client 202 as an Istorage object (i.e., an object supporting the IStorage interface). Otherwise, if IUnknown is requested, the downloaded data is provided as a file. The IStream or Istorage interface requested by the client 202 is passed to the client via the IBindStatusCallback::OnDataAvailable function (in place of the step 271 of FIG. 8B in the BindToObject function).
[0497] As with the BindToObject function, the client 202 can specify synchronous or asynchronous operation with the BindToStorage function by setting the BINDF_ASYNCHRONOUS flag in the bind information returned when the URL moniker 200 calls the client's IBindStatusCallback::GetBindInfo function. For synchronous operation, the BindToStorage function blocks execution of the client 202 during downloading of the resource designated by the URL moniker 200. For asynchronous operation, the URL moniker 200 returns immediately from the BindToStorage function, and the client 202 is not blocked.
[0498] In cases where the data is provided as the IStream or IStorage objects, the client 202 can further request asynchronous storage operation by setting the BINDF_ASYNCSTORAGE flag in the bind information returned from the client's IBindStatusCallback::GetBindInfo function. When asynchronous storage is requested, the IStream or IStorage object provided by the URL moniker 200 allows the client 202 to access the data as it is downloaded. When the client 202 call the Read function on the IStream or IStorage interface, the IStream or IStorage object returns the data if available, or returns the value E_PENDING if not yet available. Otherwise, if asynchronous storage is not requested, the IStream or IStorage object provided by the URL moniker 200 blocks the client 202 when the client calls the Read function on the object.
[0499] 6.2.9 The URL Moniker-IMoniker::Reduce Function
[0500] In the illustrated URL moniker 200, this function returns a value, MK_S_REDUCED_TO_SELF, and a pointer to itself (i.e., the pointer, “this”) as its output parameter, *ppmkReduced.
[0501] 6.2.10 The URL Moniker-IMoniker::ComposeWith Function
[0502] The illustrated URL moniker 200 supports generic composition via this function. If the function's fOnlylfNotGeneric flag is set to TRUE, the function returns the value, MK_E_NEEDGENERIC. Otherwise, the function simply returns the result of the OLE API function call, CreateGenericComposite(this, pmkRight, ppmkComposite).
[0503] 6.2.11 The URL Moniker-IMoniker::Enum Function
[0504] This function returns the value, S_OK, and sets its “*ppenummoniker” output parameter to NULL, indicating that the URL moniker 200 does not contain sub-monikers.
[0505] 6.2.12 The URL Moniker-IMoniker::IsEqual Function
[0506] This function checks another moniker specified in its pmkOtherMoniker parameter is equivalent to the URL moniker 200, meaning the other moniker also is of the URL moniker class and has a same display name (i.e., the URL string designated by the URL moniker 200). The function checks whether the other moniker's CLSID (obtained via the IPersist::GetClassID function) is CLSID_URLMoniker, and also compares the display names of the URL moniker 200 and the other moniker for equality. If the other moniker is equivalent to the URL moniker, the function returns S_OK. If not, the function returns S_FALSE.
[0507] 6.2.13 The URL Moniker-IMoniker::Hash Function
[0508] This function creates a hash value based on the URL designated by the URL moniker 200. The function typically is used to speed up comparisons by reducing the number of times that it is necessary to call the IsEqual function.
[0509] 6.2.14 The URL Moniker-IMoniker::IsRunning Function
[0510] This function returns S_OK if the URL moniker 200 is currently “running”, otherwise returns S_FALSE. The implementation of the function in the illustrated URL moniker 200 determines if the URL moniker is running by first checking whether the URL moniker is equal to the newly running moniker (i.e., by calling pmkNewlyRunning->IsEqual(this)), and next by checking whether the URL moniker 200 is registered with the Running Object Table of the bind context 156.
[0511] 6.2.15 The URL Moniker-IMoniker::GetTimeOfLastChange Function
[0512] This function returns the time of last change of an object that is registered in the running object table of the bind context 156.
[0513] 6.2.16 The URL Moniker-IMoniker::Inverse Function
[0514] This function returns the value, MK_E_NOINVERSE.
[0515] 6.2.17 The URL Moniker-IMoniker::CommonPrefixWith Function
[0516] This function computes a common prefix of the URL moniker 200 and a specified other URL moniker.
[0517] 6.2.18 The URL Moniker-IMoniker::RelativePathTo Function
[0518] This function computes a relative path between the URL moniker 200 and a specified other URL moniker.
[0519] 6.2.19 The URL Moniker-IMoniker::GetDisplayName Function
[0520] This function returns the URL string designated by the URL moniker 200. The function returns the full URL string if the URL moniker designates a full URL string. If the moniker was created with a partial URL string (as described above for the CreateURLMoniker), the function attempts to find an URL moniker which designates a base context of the URL moniker 200. The function 200 first checks in the bind context 156 under the data member, SZ_URLCONTEXT, and next checks to the left of the URL moniker if the URL moniker is part of a compound moniker. If the function does not find a base context, the function returns the partial URL string designated by the URL moniker 200.
[0521] 6.2.20 The URL Moniker-IMoniker::ParseDisplayName Function
[0522] This function parses a full or partial URL string (which is input as parameter, szDisplayName) to create a resulting URL moniker (which is output as paramter, ppmkout). If the szDisplayName parameter represents a full URL string (e.g., “http://foo.com/default.html”), the function creates a new full URL moniker which designates the full URL string. If the szDisplayName parameter represents a partial URL string (e.g., “ . . . \default.html”), the function creates a new full URL moniker which designates a full URL string formed by combining the parameter with a base context from either the SZ_URLCONTEXT object-parameter of the bind context 156 or from the URL moniker 200. For example, if the context moniker is “http://foo.com/pub/list.html” and szDisplayName is “ . . . \default.html,” the resulting URL moniker would represent “http://foo.com/default.html.” The function is used by the MkParseDisplayName (described in the Moniker Overview section above) and MkParseDisplayNameEx (described below) API functions.
[0523] 6.2.21 The URL Moniker-IMoniker::IsSystemMoniker Function
[0524] This function returns the value, S_TRUE, and outputs the value, MKSYS_URLMONIKER, as its output parameter, *pdwMksys.
[0525] 6.3 Client Extension Services
[0526] In some cases, the bind operation with the URL moniker 200 requires additional services from the client 202 in order to complete negotiations necessary for downloading the resource designated by the URL moniker from the Internet. The illustrated client 202 supports an IAuthenticate interface 230 and an IHttpNegotiate interface 232 which expose services for authentication and HTTP negotiations. The URL moniker 200 requests pointers to these interfaces using the IBindStatusCallback::QueryInterface function.
[0527] 6.4 The IAuthenticate interface
[0528] The illustrated client 202 supports the IAuthenticate interface 230 to provide a service, the authentication function, which the URL moniker 200 calls to retrieve information needed for authentication during a download. The illustrated IAuthenticate interface has the following form.
[0529] interface IAuthenticate: IUNKNOWN {
[0530] HRESULT Authenticate([out] HWND* phwnd, [out]
[0531] LPWSTR szUsername, [out] LPWSTR
[0532] szPassword);
[0533] };
[0534] The Authenticate member function of this interface is called by the URL moniker 200 when it needs basic authentication information from the client 202. In response, the client 202 can return a user name and a password strings to the URL moniker 200. Alternatively, the client can provide a window handle, HWND, of a window that is used to present a default authentication user interface. The URL moniker 200 uses the authentication user interface to obtain authentication information (i.e., the user name and password) from the user. The parameters and return values of the illustrated Authenticate function are shown in the following table.
| TABLE 35 |
|---|
| The IAuthenticate::Authenticate Function |
| Parameters and Return Values. |
[0535] 6.5 The IHttpNegotiate Interface
[0536] The URL moniker 200 utilizes the services provided by the illustrated client 200 through the IHttpNegotiate interface 232 to allow the client to negotiate HTTP download parameters. The IHttpNegotiate interface 232 has the following form.
[0537] interface IHttpNegotiate : IUnknown {
[0538] HRESULT BeginningTransaction([in] LPCWSTR
[0539] szURL, [in] DWORD dwReserved, [in] LPCWSTR
[0540] szHeaders, [out] LPWSTR szAdditionalHeaders);
[0541] HRESULT OnHeadersAvailable([in] DWORD
[0542] dwResponseCode, [in] LPCWSTR szHeaders);
[0543] HRESULT OnError[in] DWORD dwResponseCode, [in]
[0544] LPCWSTR szRequestHeaders, [in] LPCWSTR
[0545] szResponseHeaders, [out] LPWSTR
[0546] szAdditional RequestHeaders);
[0547] };
[0548] 6.5.1 The IHttpNegotiate::BeginningTransaction Function
[0549] The URL moniker 200 calls this function before sending an HTTP request for downloading the resource designated by the URL moniker. In the URL moniker's call to this function, the URL moniker notifies the client of the URL of the resource which is to be downloaded in the HTTP request. The URL moniker 200 also allows the client 202 to add additional headers to the HTTP request. The illustrated IHttpNegotiate::BeginningTransaction function has the parameters and return values shown in the following table.
| TABLE 36 |
|---|
| IHttpNegotiate::BeginningTransaction Function |
| Parameters and Return Values |
[0550] 6.5.2 The IHttpNegotiate::OnHeadersAvailable Function
[0551] This function is called by the URL moniker 200 to provide the client with the HTTP response header information used in downloading the resource designated by the URL moniker. In the function, the client 202 may examine these headers and choose to abort the HTTP transaction. The illustrated IHttpNegotiate::On HeadersAvailable function's parameters and return values are shown in the following table.
| TABLE 37 |
|---|
| IHttpNegotiate::OnHeadersAvailable Function |
| Parameters and Return Values |
[0552] 6.5.3 The IHttpNegotiate::OnError Function
[0553] The URL moniker 200 calls this function when an HTTP error occurs that cannot be resolved. The function allow the client 202 to add HTTP headers that are used to respond to the error. The function's parameters and return values are shown in the following table.
| TABLE 38 |
|---|
| IHttpNegotiate::OnError Function Parameters and Return Values |
[0554] 6.6 Display Name Parsing
[0555] With reference still to FIG. 7, the illustrated system 204 extends parsing of display names into monikers to also support the Universal Resource Indicator (URI) syntax, which is used for Internet URLs. The URI syntax specifies that a string begins with a transport protocol identifier followed by a colon character (e.g., “http:” for the Hypertext Transport Protocol, “ftp:” for the File Transport Protocol, etc.). A sub-string following the transport protocol prefix designates a resource and its site. The URI syntax is described in the IETF RFC1630 specification, which is available from the Internet at “http://ds.internic. net/rfc/rfc1590.txt.”
[0556] For parsing URI syntax display names, the illustrated system 204 provides a MkParseDisplayNameEx API function. Similar to the MkParseDisplayName API function described in the Moniker Overview section above, this API function is called by the client 202 to obtain a moniker that references data identified by a text string (referred to herein as the “display name” of the data). This is referred to herein as “parsing” the display name.
[0557] In an initial step of the parsing process, the MkParseDisplayNameEx API function parses a first portion of the display name and creates an initial moniker appropriate to that portion. For parsing with the MkParseDisplayNameEx API function, the display name is allowed to begin in one of three ways: with a program identifier (“ProgID”) followed by a colon character (“:”), with a valid file system name, or with the ‘@’ character followed by a ProgID. A ProgID is a short text string used in the Windows® operating system registry to identify applications installed on the computer system. The MkParseDisplayNameEx API function creates the initial moniker by attempting each of the following strategies in order.
[0558] “ProgID:” Case. If a prefix of the display name in the szDisplayName parameter conforms to legal ProgID syntax, is longer than a single character, and is followed by a colon character (‘:’), the API function converts the ProgID to a CLSID using the CLSIDFromProgID API function (a well known Windows® operating system API function). The MkParseDisplayNameEx API function then calls the CoCreateInstance API function (described in the Document Object and Server Overview section above) to create an object of the class identified by the CLSID (which is the initial moniker), and obtains an interface pointer to the IParseDisplayName Interface on the initial moniker.
[0559] Running Object Table Case. If a prefix of the display name is a valid file name, the MkParseDisplayNameEx API consults the running objects table for a file moniker that references the file name. If there is a running file moniker that references the display name prefix, the MkParseDisplayNameEx API treats the file moniker as the initial moniker.
[0560] File System Case. The MkParseDisplayNameEx API function consults the file system of the computer 20 (FIG. 1) to check whether a prefix of the display name matches any existing file in the file system. The MkParseDisplayNameEx API function then creates a file moniker (as described in the Moniker Overview section above) which references this file as its initial moniker. “@ProgID” Case. If the initial character of the display name is the ‘@’ character, the MkParseDisplayNameEx API function converts a portion of the display name following the ‘@’ character which conforms to the ProgID syntax into a CLSID using the CLSIDFromProgID API function. The MkParseDisplayNameEx API function then creates a instance of the class identified by the CLSID (which is the initial moniker).
[0561] The MkParseDisplayNameEx API function then iteratively calls the IParseDisplayName::ParseDisplayName function of the moniker it has created thus far (the “current” moniker), passing a suffix portion of the display name which remains to be parsed (the “current” portion) in the call. The ParseDisplayName function parses this remaining portion of the display name into a new moniker, and returns the new moniker with a new suffix portion of the display name that remains to be parsed. The returned moniker and display name portion become the current moniker and current portion in the next iteration of this step. The iterations end when the display name is fully parsed, an error occurs, or the remaining suffix of the display name cannot be parsed. As a result of the iterative parsing, the MkParseDisplayNameEx API function creates a succesion of increasingly more specific monikers which it combines into a composite moniker. Each successive moniker is able to parse a next more specific portion of the display name into a moniker. For example, a display name can be parsed by the API function into a composite moniker which includes a file moniker that references a file designated in the display name, and an item moniker that references a part of the file designated in a further portion of the display name.
[0562] The MkParseDisplayNameEx API function supports the URI syntax in an extensible fashion with the “ProgID:” case strategy for parsing the display name prefix to an initial moniker. In the illustrated embodiment, the display name prefixes that designate Internet transport protocols (e.g., “http:,” “ftp:,” and “gopher:”) are registered as ProgIDs in the system registry which map to a CLSID for the URL moniker. Thus, when the MkParseDisplayNameEx API function is called to parse an URL, the MkParseDisplayNameEx API function creates a URL moniker in its initial parsing step, and calls the URL moniker's IParseDisplayName::ParseDisplayName function to parse the remainder of the URL. Likewise, the MkParseDisplayNameEx API function can be extended to parse display names with new transport protocols by registering the protocol identifier as a ProgID in the system registery that maps to a handler moniker, and implementing a ParseDislayName function in the handler moniker to parse display names using the protocol.
[0563] The MkParseDisplayNameEx API function is defined as shown in the following C programming language statement, and has the parameters and return values shown in the following table 39.
[0564] HRESULT MkParseDisplayNameEx([in] IBindCtx* pbc, [in] LPWSTR szDisplayName, [out] ULONG* pcchEaten, [out] IMoniker** ppmk);
| TABLE 38 |
|---|
| MkParseDisplayNameEx API Function Parameters and Return Values |
[0565] 7. Hyperlink Navigation Architecture
[0566] With reference to FIG. 9, the illustrated embodiment of the invention provides a object-oriented framework or architecture 300 for unified hyperlink navigation between any documents, objects and applications. In particular, this unified hyperlink navigation is not limited to just HTML documents of the World-Wide Web, or to hyperlinking within a single application such as a web browser. The illustrated architecture 300 supports each of the following forms of hyperlink navigation:
[0567] From a standalone application to another standalone application, neither of which implements document objects;
[0568] From a standalone application to a document object or HTML document hosted in the browser of FIG. 2;
[0569] From a document object in the browser of FIG. 2 to another document object in the same browser;
[0570] From a document object in the browser of FIG. 2 to a document object embedded in a binder document (a document which contains one or more document objects, which may have different types) hosted in a binder application (e.g., the Microsoft® Office Binder application in the Microsoft® Office 95 application suite); and
[0571] From one location in a document object (or a document displayed by a standalone application) to another location in the same document object (or standalone application document).
[0572] The architecture 300 comprises a set of system provided services and a set of integration interfaces and objects which support the unified hyperlink navigation.
[0573] 7.1 Hyperlink Navigation Overview
[0574] A hyperlink in the illustrated architecture 300 is a reference to another location in a document or object. The location can be in the same document or object in which the hyperlink appears, or in a new document or object. The document's or object's data can be stored in a file of the computer's file system, a resource residing at a site on the Internet, or any arbitrary location that can be referenced by a moniker. The illustrated hyperlink reference is a (target, location) tuple. The target portion of the tuple is stored as a moniker, and the location portion is stored as a string. The hyperlink can be navigated by binding to the target, and then requesting that the target navigate to the location. When the document or object that contains a hyperlink is displayed, the illustrated hyperlink is presented as colored and/or underlined text, as “hot spot” regions on an image, as push buttons, or other user interface control. The appearance of the hyperlink, however, is dependent on the document or object which contains the hyperlink and the context of the hyperlink. The illustrated architecture does not impose any requirements limiting the presentation of hyperlinks, although preferably the hyperlinks should be made obvious, e.g., via coloring, underlining, or by changing the cursor or displaying “tool tips” (i.e., a small descriptive text box) when a mouse cursor passes over the hyperlink.
[0575] Hyperlink navigation involves a transition (also known as a “jump”) from one document, object, or application (referred to as the “hyperlink container”) to another document, object, or application (referred to as the “hyperlink target”). Both the hyperlink container and target usually remain running, but the hyperlink target visually replaces the hyperlink container. In cases where the containing document or object and the target document or object are displayed in a same application (e.g., the browser window 68 of FIG. 2), the target document or object is displayed in place of the containing document or object in that application's window (e.g., within the document display area 72 of FIG. 2). In cases where the target document or object is displayed with a different application than the hyperlink container, the illustrated architecture 300 creates the appearance of window reuse by passing the window position and size of the hyperlink container application to the target, having the target's application size and position its window in the same location on the computer's display, and hiding the container application's window.
[0576] Hyperlink navigation utilizes a global context (referred to herein as the “browse context”) which records each hyperlink navigation transition and chains the transitions in order of their occurrence as a “navigation stack.” This context allows traversing previous hyperlink transitions in forward or reverse directions, such as with “go back” or “go forward” commands (e.g., back and forward buttons 490-491 in the toolbar 480 (FIG. 12) of the browser window 68 (FIG. 2)). The browse context is global in scope and includes hyperlink transitions between applications. However, a single user can maintain multiple separate browse contexts concurrently, such as for running two instances of the browser in separate browser windows 68 (FIG. 2).
[0577] 7.2 Hyperlink Navigation Architecture Overview
[0578] Referring still to FIG. 9, the illustrated hyperlink navigation architecture 300 includes some components which are provided by the operating system of the computer 20 (FIG. 1) and other user-defined components that integrate with the architecture 300 by supporting interfaces described below.
[0579] 7.2.1 “Simple” Hyperlinking API Functions
[0580] The architecture 300 allows application programs to participate in hyperlink navigation at different levels. For minimal participation in hyperlink navigation (e.g., to allow navigation from the application to a hyperlink target), an application program can utilize a set of system API functions (referred to herein as simple hyperlinking API functions), which include the HlinkSimpleNavigateToString, HlinkSimpleNavigateToMoniker, HlinkNavigateString, HlinkNavigateMoniker, HlinkGoBack, and HlinkGoForward API functions described below. An application can implement the additional objects and integration interfaces described below to support more complex hyperlink navigation features, such as navigation to a sub-location within a document or object, or cut and paste as well as drag and drop operations with hyperlinks. Thus, an application such as an Internet browser which is a viewer of documents that contain hyperlinks would implement the objects and integration interfaces so as to support all hyperlink navigation features. On the other hand, another application without implementing the objects and integration interfaces can use the simple hyperlinking API function to provide simpler hyperlink features, such as a menu command or button control which hyperlinks to the application developer's home page or to a help or customer technical support page on the World Wide Web.
[0581] 7.2.2 Hyperlink Target
[0582] A hyperlink target is a destination of hyperlink navigation. In the illustrated architecture 300, hyperlink targets can be an object (referred to as a hyperlink target object 310) that supports an IHlinkTarget interface 312 described below, an object that supports the IOleObject interface (a well known OLE interface), or a file that can be viewed by launching a viewer application program via the shell execute operating system service as described above. For full integration with the architecture 300, a document which is to be a hyperlink target preferably is encapsulated as a hyperlink target object 310 which supports the HlinkTarget interface 312. Objects and documents which do not support the IHlinkTarget interface 312 also can act as a hyperlink target, but do not provide the internal navigation feature (i.e., hyperlink navigation to an internal location of a document) available through this interface and do not have access to the browse context that holds the navigation stack described above.
[0583] 7.2.3 Hyperlink Object
[0584] In the illustrated architecture 300, hyperlink navigation is performed using hyperlink objects 320-321. Each hyperlink object 320-321 implements an IHlink interface 322 and encapsulates four pieces of reference information that characterize a hyperlink: a moniker (hereafter “hyperlink target moniker”) to the hyperlink's target (e.g., hyperlink target object 310), a string for referencing a sub-location within the target, a descriptive name for the target (hereafter “friendly name”), and additional parameters. The moniker can be of any type. Where the hyperlink target is a resource residing on the remote computer 58 (FIG. 2), a URL moniker or other asynchronous moniker preferably is used as the hyperlink target moniker. Where the hyperlink target resides as a file in the file system on the computer 20 (FIG. 2) or on a connected LAN, a file moniker preferably is used as the hyperlink target moniker.
[0585] The illustrated hyperlink objects 320-321 support the IPersistStream, and IDataObject interfaces (which are well known OLE interfaces), in addition to the IHlink interface 322. The hyperlink objects 320-321 include member functions which implement the behavior of navigating to the location in the target which is referenced by the hyperlink object, and are exposed through the IHlink interface 322. The hyperlink objects 320-321 also expose functions via the IPersistStream interface to save and load itself in the computer's secondary storage 42, and functions via the IDataObject interface for transferring itself between applications with cut, copy and paste operations using the clipboard as well as drag-and-drop operations. A document can use the hyperlink object to represent hyperlinks contained in the document, thus encapsulating the functionality of hyperlink navigation, as well as saving, loading, dragging, dropping, cutting and pasting of the hyperlinks.
[0586] The hyperlink objects 320-321 in the illustrated architecture are system-provided objects. Documents and objects which contain hyperlinks can create hyperlink objects via HlinkCreateFromData, HlinkCreateFromMoniker, HlinkCreateFromString, and OleLoadFromStream API functions described more fully below.
[0587] 7.2.4 Hyperlink Container and Hyperlink Sites
[0588] A hyperlink container 330 in the illustrated architecture 300 is a document or application that contains hyperlinks. More specifically, the hyperlink container 330 can be a document object (described above) or an object implemented by an application program. Often, hyperlink containers also act as hyperlink targets. The illustrated hyperlink container 330 also acts as a hyperlink target, and supports the IHlinkTarget interface 312.
[0589] Hyperlink containers which use hyperlink objects for hyperlink navigation optionally can implement hyperlink site objects for each of the hyperlink objects. The illustrated hyperlink container 330 includes hyperlink site objects 334-335 for the hyperlink objects 320-321. The hyperlink site objects 334-335 support an IHlinkSite interface 338, and are used by their corresponding hyperlink objects 320-321 to retrieve a moniker that references the hyperlink container 330. The hyperlink objects 320-321 use this moniker to evaluate monikers which reference hyperlink targets relative to the hyperlink container. For example, the hyperlink target moniker contained in the hyperlink object 320 is null, which indicates the hyperlink target is the hyperlink container 330 (such as for an internal jump to a particular location within the hyperlink container). Accordingly, the hyperlink object 320 uses the hyperlink site 334 to efficiently navigate this internal jump.
[0590] 7.2.5 Hyperlink Frame
[0591] A hyperlink frame object 340 acts as an outer frame that manages one or more hyperlink container documents. Referring more specifically to FIG. 2, the illustrated hyperlink frame object 340 is the browser that runs on the computer 20 and displays the window 68. In the window 68, the browser provides a document viewing user interface in the form of a frame 70 with user interface controls 74 and a document display area 72. The illustrated hyperlink frame object 340 operates as a host or container for document objects provided by a server application, and allows such a document object to display its document in the display area 72 for viewing by the user. For managing multiple hyperlink target document types, the illustrated hyperlink frame object 340 supports an IHlinkFrame interface 342.
[0592] 7.2.6 Hyperlink Browse Context
[0593] The illustrated architecture includes a hyperlink browse context object 350 which supports an IBrowseContext interface 352. The hyperlink browse context object 350 is a system provided object which maintains a navigation stack 354 for tracking hyperlink navigation transitions. The hyperlink browse context object 350 is passed between the components involved in hyperlinking to provide access to the navigation stack.
[0594] In addition to the navigation stack, the hyperlink browse context object 350 also contains other context information. The hyperlink browse context object 350 maintains information to enable or disable “go back” and “go forward” navigation commands. The object 350 also stores window position and hyperlink navigation toolbar position information 356 for use in positioning a window of the hyperlink target's hyperlink frame 341 over that of the hyperlink container as well as the hyperlink navigation toolbar 480 (FIG. 12) within the window to provide a perception of window reuse.
[0595] When a hyperlink target (e.g., objects 310, 330) is navigated for a first time, the hyperlink browse context object 350 is passed to the hyperlink target (using the IHlinkTarget::SetBrowseContext function described below). The hyperlink target registers with the hyperlink browse context object 350 (using the IHlinkBrowseContext::Register function described below). When the hyperlink target is again navigated, the hyperlink target also notifies the hyperlink browse context object 350 using the IHlinkBrowseContext::OnNavigateHlink function described below. In response to these notifications, the hyperlink browse context object 350 updates the navigation stack so as to add the newly navigated hyperlink target and to record the currently navigated hyperlink target in the navigation stack.
[0596] The hyperlink browse context object 350 also utilizes the notifications to manage the lifetimes of registered hyperlink target applications using a MRU (most recently used) scheme. When a hyperlink is navigated to a new hyperlink target (i.e., other than an internal hyperlink navigation to a new location within the hyperlink container), the hyperlink target is displayed and the hyperlink container hidden. Although no longer displayed, the hyperlink container remains a running object which is stored in a cache portion of the memory 26 in the computer 20 (FIG. 1). The hyperlink browse context object keeps a reference to this object in a running objects table 358.
[0597] The cache and running objects table 358 are updated according to a least recently used scheme. Specifically, when a new object is added to the cache and running objects table 358, the least recently used running object is dropped from the cache and running objects table 358. When an object is removed from the running objects table, the hyperlink browse context still maintains the original reference to the object's data in the navigation stack.
[0598] Since the hyperlink container and other recently used objects are kept in their running state in the cache, the hyperlink navigation architecture allows quicker return navigation to these objects (such as with the history drop down list 499, back button 490, and forward button 491 on the hyperlink navigation toolbar 480 of FIG. 12). When navigating to a hyperlink target, the running objects table 358 is first consulted. If the hyperlink target is in the running objects table 358, the running hyperlink target can be immediately displayed. Otherwise, navigating to the hyperlink target requires loading the hyperlink target's server application, instantiating the hyperlink target, and retrieving the hyperlink target's data from its original source (e.g., from the Internet).
[0599] 7.3 Simple Hyperlinking Process
[0600] FIG. 10 shows a process 400 for simple hyperlink navigation between a hyperlink container and a hyperlink target, neither of which directly use the hyperlinking browse context object 350 (FIG. 9). In the illustrated simple hyperlink navigation process 400, the hyperlink container and hyperlink target are documents or objects which are hosted by one or both of the hyperlink frame objects 340-341 (i.e., displayed within the document display area 72 of FIG. 2 which the hyperlink frame object provides). In the process 400, the hyperlink frame objects 340-341 take responsibility for integrating with the hyperlink browse context object 350 to maintain the navigation stack, along with features such as history and favorites lists. This simplifies the support for hyperlinking navigation that the hyperlink container and hyperlink target must provide.
[0601] At a first step 402 of the process 400, the hyperlink container 330 initiates hyperlink navigation using one of the “simple hyperlinking” APIs when the user activates a hyperlink. The following pseudo-code is an example of code in the hyperlink container 330 for initiating hyperlink navigation.
[0602] // do the navigation
[0603] HlinkSimpleNavigateToString( “http://www.microsoft.com/foo.htm”,
[0604] NULL, NULL, punkMe, 0, pbc, pbsc, 0);
[0605] The simple hyperlinking API function calls the IHlinkFrame::Navigate function of the hyperlink frame object 340 (e.g., the browser of FIG. 2) at step 403. The hyperlink frame object's IHlinkFrame::Navigate function packages the simple hyperlinking API function's call into a call to the IHlink::Navigate function of a hyperlink object as shown at step 405. The hyperlink frame object 340 may simply set some flags and defer to the hyperlink object's IHlink::Navigate function (as demonstrated in the example code for step 454 of the process shown in FIG. 11 described below). However, the procedure of calling the IHlink::Navigate through the hyperlink frame object 340 also affords the hyperlink frame object the chance to provide an integrated user-interface, progress feedback, cancellation options, and other features as indicated at step 404. For displaying progress indication and cancellation user interface controls, the hyperlink frame object 340 can register an IBindStatusCallback interface of its own callback object at the step 404 with the browse context 358 so as to receive progress notification call backs during navigation. At step 405, the hyperlink frame object calls the hyperlink object's IHlink::Navigate function.
[0606] In the IHlink::Navigate function at step 406, the hyperlink object 320-321 navigates to the hyperlink target, such as by binding with the hyperlink target moniker. After completing navigation to the hyperlink target, the hyperlink object calls the hyperlink target's IHlinkTarget::Navigate function at step 407.
[0607] At step 408 in the IHlinkTarget::Navigate function, the hyperlink target navigates to the specific location within the target indicated by the hyperlink (if any). Typically, this involves the hyperlink object interpreting the location string of the hyperlink and completing hyperlink navigation accordingly. The following pseudo-code is an example implementation of the IHlinkTarget::Navigate function within the hyperlink target object 310.
[0608] IHlinkTarget::Navigate(DWORD grfHLNF, LPCWSTR szLocation)
[0609] {
[0610] IHlinkFrame* phIFrame = NULL;
[0611] // if szLocation is not visible show it
[0612] // if this hyperlink target is an OLE Document Object, try
[0613] to retrieve the hyperlink frame pointer from the
[0614] IOleInPlaceFrame
[0615] if (m_poleinplaceframe)
[0616] m_poleinplaceframe->
[0617] QueryInterface(IID_IHlinkFrame,
[0618] (void**)&phIFrame);
[0619] // notify the hlink frame and the browse context that the
[0620] navigation is complete. Note: either phlFrame or
[0621] m_phlbc may be NULL
[0622] HlinkOnNavigate(phlFrame, NULL, grfHLNF, m_pmk,
[0623] szLocation, szFriendlyName);
[0624] m_fHide = FALSE;
[0625] m_fHideFrame = FALSE;
[0626] } // IHlinkTarget::Navigate
[0627] At step 409, the hyperlink target then calls the IHlinkFrame::OnNavigate function of its hyperlink frame object 341. In the OnNavigate function at step 410, the hyperlink frame object 341 repositions its window 68 (FIG. 2) and updates the window's visibility. If the hyperlink target's hyperlink frame object is the same as that of the hyperlink container, the hyperlink frame object sets flags (as demonstrated in the example pseudo-code for the step 464 of FIG. 11 described below) to keep its window visible.
[0628] Otherwise, if the hyperlink frame objects 340-341 of the hyperlink container 330 and hyperlink target 310 are different, the hyperlink frame object 341 of the hyperlink target 310 positions its window 68 (FIG. 2) and hyperlink navigation toolbar 380 (FIG. 12) according to the position information in the browse context (i.e., over the position of the window of the hyperlink frame object 340 of the hyperlink container 330. Then, the window of the hyperlink frame object 341 of the hyperlink target 310 is made visible, while the window of the hyperlink frame object 340 of the hyperlink container 330 is hidden. This creates the appearance of replacing the hyperlink container with the hyperlink target within a same window.
[0629] 7.4 Full Hyperlink Navigation Process
[0630] FIG. 11 shows a process 450 for hyperlink navigation between a hyperlink container and a hyperlink target which integrate directly with the hyperlinking browse context object 350 (FIG. 9). This integration allows the hyperlink container and target to provide more complex features, such as cut, copy and paste operations and drag and drop operations.
[0631] At an initial step 452 before any navigation occurs, the hyperlink container 330 obtains a hyperlink object 320-321 which represents the hyperlink. The hyperlink container 330 either creates the hyperlink object 320-321 using the HlinkCreateFromData, HlinkCreateFromMoniker, or HlinkCreateFromString API functions (described below), or by loading a stored hyperlink object from its persistent data using the OleLoadFromStream API function (a well known OLE API function). At step 453, the hyperlink container 330 initializes the hyperlink object 320-321 using an IHlink::SetHlinkSite function of the hyperlink object. In its call to IHlink::SetHlinkSite, the hyperlink container passes an IHlinkSite interface pointer of the hyperlink container's hyperlink site 334-335 and data specific to the hyperlink through a dwSiteData parameter of the function call. The hyperlink container 330 can use a same hyperlink site 334-335 to service multiple hyperlink objects 320-321.
[0632] When the user activates the hyperlink, the hyperlink container 330 at step 454 registers itself with the browse context object 350 to ensure that the hyperlink container is included in the navigation stack, so that the user can return to the hyperlink container with the “go back” command feature. The hyperlink container 330 also obtains the position of the window in which it is displayed from the hyperlink frame object 340 and the position of the hyperlink navigation toolbar 480 (FIG. 12) within the window, and registers this position information with the hyperlink browse context object 350. As in the simple hyperlinking process 400, the position information is used in appropriately positioning the window of the hyperlink target's frame when the hyperlink target is hosted within a different hyperlink frame object 341 so as to create the appearance of window reuse. The following pseudo-code is an example of the implementation of the step 454 in the hyperlink container.
[0633] // retrieve the hyperlink frame pointer
[0634] if (!m_fTriedToGetFrame && m_poleinplaceframe && m_phlframe
[0635] == NULL) {
[0636] m_fTriedToGetFrame = TRUE;
[0637] m poleinplaceframe->QueryInterface(IID_IHlinkFrame,
[0638] (void**)&m_phlFrame);
[0639] }
[0640] if (mphlbc == NULL){
[0641] // get the browse context pointer
[0642] if (m_phlFrame)
[0643] m_phlFrame->GetBrowseContext(&m_phlbc);
[0644] else
[0645] HlinkCreateBrowseContext(&m phlbc);
[0646] if (m_phlbc == NULL) return E_FAIL;
[0647] // register with the browse context
[0648] m_phlbc->Register(pmkThis, phls, &m_dwRegister);
[0649] // because we want the user to be able to come back this
[0650] object via GoBack functionality add
[0651] // self to the navigation stack. This effectively tells the
[0652] browse context that the current hyperlink container
[0653] // referred to by pmkThis is a member (at the top) of the
[0654] navigation stack
[0655] m_phlbc->OnNavigateHlink(NULL, pmkThis, szLocation,
[0656] szFriendlyName);
[0657] }
[0658] if (m_phIframe == NULL) {
[0659] HLBWINFO hlbwinfo;
[0660] // initialize hlbwinfo with window locations and flags
[0661] // register the browse window info in the browse context
[0662] so it is later available to the hyperlink target and
[0663] m_phlbc->SetBrowseWindowInfo(&hlbwinfo)
[0664] // set the flag indicating that this window should be hidden
[0665] after navigation. But this flag
[0666] // is cleared in the IHlinkTarget::Navigate and
[0667] IHlinkFrame::OnNavigate methods.
[0668] m_fHide = TRUE;
[0669] v_fHideAppFrame = TRUE; // only the MDI applications need this separate flag
[0670] else {
[0671] m_fHide = FALSE;
[0672] v_fHideAppFrame = FALSE;
[0673] }
[0674] hr = HlinkNavigate(pkl, m_phlframe, NULL, pbc /* could be NULL
[0675] */, plbsc, m_phlbc);
[0676] if (hr == NOERROR){
[0677] if (m_fHide)
[0678] // Hide this document
[0679] if (m_vfHideAppFrame)
[0680] // Hide/Minimize application's frame window
[0681] }
[0682] The hyperlink container 330 next calls the IHlinkFrame::Navigate function of the hyperlink frame object 340 (e.g., the browser application 68 of FIG. 2) at step 455. The hyperlink frame object's IHlinkFrame::Navigate function may simply set some flags and defer to the hyperlink object's IHlink::Navigate function. However, the procedure of calling the IHlink::Navigate through the hyperlink frame object 340 also affords the hyperlink frame object the chance to provide an integrated user-interface, progress feedback, cancellation options, and other features as indicated at step 457. For displaying progress indication and cancellation user interface controls, the hyperlink frame object 340 can register an IBindStatusCallback interface of its own callback object at the step 457 with the browse context 358 so as to receive progress notification call backs during navigation. At step 458, the hyperlink frame object calls the hyperlink object's IHlink::Navigate function. The following pseudo-code is an example implementation of the IHlinkFrame::Navigate function in the hyperlink frame object 340.
[0683] HlinkFrame::Navigate(DWORD grfHLNF, IBindCtx* pbc,
[0684] IBindStatusCallback* pbsc, IHlink* phlDest)
[0685] // This flag gets cleared in IHlinkFrame::OnNavigate( ).
[0686] Thus if the Navigation within the same
[0687] // frame window then we will get the right behavior as this
[0688] flag gets cleared in the OnNavigate( )
[0689] // method.
[0690] m_fHide = TRUE;
[0691] // some frames need only the following function so that
[0692] they can properly show and hide themselves.
[0693] // others may hook themselves in to the
[0694] IBindStatusCallback for progress notification
[0695] hr =IHlink::Navigate(NULL, pbc, pbsc, phlDest);
[0696] if (SUCCEEDED(hr) && m_fHide)
[0697] // Hide the frame window
[0698] } // IHlinkFrame::Navigate
[0699] In the IHlink::Navigate function at step 459, the hyperlink object 320-321 navigates to the hyperlink target, such as by binding with the hyperlink target moniker. When navigation to the hyperlink target is complete, the hyperlink object 320-321 passes the hyperlink browse context 350 to the hyperlink target via the IHlinkTarget::SetBrowseContext function at step 460. The hyperlink object 320-321 then calls the hyperlink target's IHlinkTarget::Navigate function at step 461 to navigate to a specific location within the target. The following pseudo-code is an example implementation of the IHlink::Navigate function.
| IHlink::Navigate(DWORD grfHLNF, IBindCtx* pbc, |
| IBindStatusCallback*pbsc, IHlinkBrowseContext* phlbc) |
| { |
| IHlinkTarget* phlTarget = NULL; |
| IMoniker* pmkLeft = NULL; |
| if (grfHLNF & HLNF_USEBROWSECONTEXTCLONE) { |
| grfHLNF &= |
| ˜HLNF_USEBROWSECONTEXTCLONE; |
| phlbc->Clone(NULL, IID_IHlinkBrowseContext, |
| &phlbc); |
| } |
| else { |
| hr = m_phlSite->GetMoniker(m_dwSiteData, |
| OLEGETMONIKER_ONLYIFTHERE, |
| OLEWHICHMK_CONTIANER, &pmkLeft); |
| if (FAILED(hr) ∥ m_pmkTarget->IsEqual(pmkLeft)) { |
| hr = m_phlsite->GetInterface(dwSiteData, 0, |
| IID_IHlinkTarget, (void**)&phlTarget); |
| if (FAILED(hr)) |
| phlbc->GetObject(m_pmkTarget, |
| &phlTarget); |
| } } |
| if (phlTarget == NULL) { |
| // Set the pbsc in the pbc to get asynch and |
| notification binding behavior requested by caller |
| m_pmkTarget->BindToObject(pmkLeft, |
| IID_IHlinkTarget, &phlTarget); |
| phlTarget->SetBrowseContext(phlbc); |
| } |
| phlTarget->Navigate(grfHLNF, m_szLocation); |
| }// IHlink::Navigate |
[0700] As remarked above, the hyperlink container'shyperlink frame object 340 passes the hyperlink in browse context object 350 to the hyperlink target 310 via the IHlinkTarget::Set BrowseContect function at the step 460. This allows the hyperlink target to access the navigation stack and the position information from the hyperlink browse context object. The following pseudo-code is an example implementation of the IHlinkTarget::SetBrowseContext function.
[0701] IHlinkTarget::SetBrowseContext(IHlinkBrowseContext* phlbc)
[0702] {
[0703] if (m_phlbc != NULL){
[0704] m_phlbc->Revoke(m_dwRegister);
[0705] m_phlbc->Release( );
[0706] }
[0707] m_phlbc = phlbc;
[0708] if (m_phlbc != NULL) {
[0709] m_phlbc->AddRef( );
[0710] m_phlbc->Register(0, (IUNKNOWN*)this, m_pmk,
[0711] &m dwRegister);
[0712] }
[0713] return S_OK;
[0714] } // CHlinkTarget::SetBrowseContext
[0715] At step 462 in the IHlinkTarget::Navigate function, the hyperlink target navigates to the specific location within the target indicated by the hyperlink (if any). Typically, this involves the hyperlink object interpreting the location string of the hyperlink and completing hyperlink navigation accordingly. The following pseudo-code is an example implementation of the IHlinkTarget::Navigate function within the hyperlink target object 310.
[0716] IHlinkTarget::Navigate(DWORD grfHLNF, LPCWSTR szLocation)
[0717] {
[0718] IHlinkFrame* phlFrame = NULL;
[0719] // if the object is not visible, activate it and show it. jump
[0720] to the location indicated by szLocation
[0721] // if this hyperlink target is an OLE Document Object, try
[0722] to retrieve the hyperlink frame pointer from the
[0723] lOlelnPlaceFrame
[0724] if (m_poleinplaceframe)
[0725] m_poleinplaceframe->
[0726] QueryInterface(IID_IHlinkFrame,
[0727] (void**)&phlFrame);
[0728] // notify the hlink frame and the browse context that the
[0729] navigation is complete. Note: either phlFrame or
[0730] m_rphlbc may be NULL
[0731] HlinkOnNavigate(phlFrame, m_phlbc, grfHLNF, m_pmk,
[0732] szLocation, szFriendlyName);
[0733] if (phlframe == NULL && !(grfHLNF &
[0734] HLNF_INTERNALJUMP)) {
[0735] HLBWINFO hlbwi;
[0736] phlbc->GetBrowseWindowInfo(&hlbwi);
[0737] // adjust the document and frame windows according
[0738] to the dimensions in hlbwi
[0739] }
[0740] m_fHide = FALSE;
[0741] m fHideFrame = FALSE;
[0742] } // IHlinkTarget::Navigate
[0743] At step 463, the hyperlink target then calls the IHlinkFrame::OnNavigate function of its hyperlink frame object 341. In the OnNavigate function at step 464, the hyperlink frame object 341 repositions its window 68 (FIG. 2) and updates the window's visibility. If the hyperlink target's hyperlink frame object is the same as that of the hyperlink container, the hyperlink frame object sets an m_fHide flag to ensure that the frame remains visible. The following pseudo-code is an example implementation of the IHlinkFrame::OnNavigate function.
[0744] IHlinkFrame::OnNavigate(DWORD grfHLNF)
[0745] {
[0746] if (!(grfHLNF & HLNF_INTERNALJUMP)) {
[0747] HLBWINFO hlbwi;
[0748] m_phlbc->GetBrowseWindowInfo(&hlbwi);
[0749] // Adjust this document/frame windows according to
[0750] the dimensions in hlbwi
[0751] }
[0752] m_fHide = FALSE;
[0753] } // IHlinkFrame::OnNavigate
[0754] Finally, at step 465, the hyperlink browse context object 350 receives notification of a successful navigation from the hyperlink target (within the IHlinkTarget::Navigate function) with a call to the hyperlink browse context object's IHlinkBrowseContext::OnNavigateHlink function. This allows the hyperlink browse context object to update the navigation stack. The following pseudo-code shows an example implementation of the IHlinkBrowseContext::OnNavigateHlink function.
[0755] IHlinkBrowseContext::OnNavigateHlink(DWORD grfHLNF,
[0756] Moniker* pmkTarget, LPCWSTR szLocation, LPCWSTR
[0757] szFriendlyName)
[0758] {
[0759] // if CreateNoHistory or NavigatingToStackitem, return
[0760] immediately
[0761] // unless NavigatingBack or NavigatingForward is also set
[0762] if (grfHLNF & (HLNF_CREATENOHISTORY
[0763] HLNF_NAVIGATINGTOSTACKITEM)) {
[0764] if (!(grfHLNF & (HLNF_NAVIGATINGBACK |
[0765] HLNF_NAVIGATINGFORWARD)))
[0766] return NOERROR;
[0767] }
[0768] if (grfHLNF & HLNF_NAVIGATINGBACK)
[0769] --m_iCurrent;
[0770] else if (grfHLNF & HLNF_NAVIGATINGFORWARD)
[0771] ++m_iCurrent;
[0772] else {
[0773] // Add this hyperlink to the navigation stack at
[0774] m_iCurrent+1, remove all items greater than
[0775] m_iCurrent+1,
[0776] ++m_iCurrent;
[0777] }
[0778] } // IHlinkBrowseContext:OnNavigateHlink
[0779] 7.5 Hyperlinking Interfaces
[0780] The hyperlink architecture 300 integrates the various components involved in hyperlink navigation with hyperlink interfaces. The hyperlink interfaces of the illustrated hyperlink architecture 300 are defined as follows:
| typedef enum tagHLNF { |
[0781] 7.6 Hyperlinking Architecture Data Structures
[0782] 7.6.1 The HLNF Enumeration
[0783] The HLNF enumeration defines values that are used to indicate how hyperlink navigation is to proceed, and also convey contextual information about the navigation from each of the objects in the architecture 300 to the others. The values of the HLNF enumeration in the illustrated architecture 300 are shown in the following table.
| TABLE 39 |
|---|
| HLNF Enumeration Values |
[0784] 7.6.2 The HLINKWHICHMK Enumeration
[0785] The HLINKWHICHMK enumeration defines values which are passed to an IHlinkSite::GetMoniker function (described below) to specify whether the function call is requesting the moniker for the container document or a base moniker specific to the site. The values of the HLINKWHICHMK enumeration in the illustrated architecture 300 are shown in the following table.
| TABLE 40 |
|---|
| HLINKWHICHMK Enumeration Values. |
[0786] 7.6.3 The HLINKGETREF Enumeration
[0787] The HLINKGETREF enumeration defines values that are passed to an IHlink::GetMonikerReference and IHlink::GetStringReference functions (described below) to specify whether the function call is requesting the absolute reference for the hyperlink target. The values of the HLINKGETREF enumeration in the illustrated architecture 300 are shown in the following table.
| TABLE 41 |
|---|
| HLINKGETREF Enumeration Values |
[0788] 7.6.4 The HLFNAMEF Enumeration
[0789] The HLFNAMEF enumeration defines values that are passed to an IHlink::GetFriendlyName function (described below) to specify which friendly name the function call is requesting. The values of the HLFNAMEF enumeration in the illustrated architecture 300 are shown in the following table.
| TABLE 42 |
|---|
| HLFNAMEF Enumeration Values. |
[0790] 7.6.5 The HLINKMISC Enumeration
[0791] The HLINKMISC enumeration defines values that are returned from an IHlink::GetMiscStatus function (described below) specifying whether the hyperlink object is a relative or an absolute hyperlink. The values of the HLINKMISC enumeration are shown in the following table.
| TABLE 43 |
|---|
| HLINKMISC Enumeration Values |
[0792] 7.6.6 The HLITEM Structure
[0793] This structure is returned from an IEnumHLITEM::Next function (described below) based on enumerators returned from an IHlinkBrowseContext::EnumNavigationStack function (described below). The values which are contained in the illustrated HLITEM structure are shown in the following table.
| TABLE 44 |
|---|
| HLITEM Structure Values. |
[0794] 7.6.7 The HLBWIF Enumeration
[0795] The HLBWIF enumeration defines flags that are passed as part of an HLBWINFO structure (described below) which is associated with the hyperlink browse context 350. The HLBWINFO structure is retrieved from the hyperlink browse context object 350 using an IHlinkBrowseContext::GetBrowseWindowContext function (described below), and put into the hyperlink browse context object using an IHlinkBrowseContext::SetBrowseWindowContext function (described below). The values of the HLBWIF enumeration in the illustrated architecture 300 are shown in the following table.
| TABLE 45 |
|---|
| HLBWIF Enumeration Values |
[0796] 7.6.8 The HLBWINFO Structure
[0797] This data structure in the hyperlink browse context object 350 contains information relating to the locations and sizes of frame- and document-level windows of the browse context. The HLBWINFO structure is retrieved from the hyperlink browse context object 350 using an IHlinkBrowseContext::GetBrowseWindowContext function (described below), and put into the browse context using an IHlinkBrowseContext::SetBrowseWindowContext function (also described below). In the simple hyperlinking process 400 (FIG. 10) and the full hyperlinking process 450 (FIG. 11) described above, the hyperlink target 310 retrieves the HLBWINFO structure within the IHlinkTarget::Navigate function in order to reposition the hyperlink target's, user interface properly and ensure as seamless a transition as possible to the hyperlink target. The values held in the HLBWINFO structure in the illustrated architecture 300 are shown in the following table.
| TABLE 46 |
|---|
| HLBWINFO Structure. |
[0798] 7.6.9 The HLID Constants
[0799] For convenience and performance, individual hyperlink objects 320-321 are identified in the navigation stack which is maintained in the illustrated browse context 350 (and in a history/favorites list feature) using a hyperlink identifier (referred to herein as an HLID), rather than as an IHlink interface pointer. This prevents unnecessary passing of interface pointers across process boundaries in common user-interface scenarios, such as building a drop-down menu or scrollable list of the history, or when testing the current location in the navigation stack to enable “Go Back” and “Go Forward” features. The following table shows HLID values that are reserved in the illustrated architecture 300 to identify logical positions within a navigation stack.
| TABLE 47 |
|---|
| HLID Constants. |
[0800] 7.6.10 The HLQF Enumeration
[0801] The HLQF enumeration defines values that are passed to an IHlinkBrowseContext::QueryHlink function (described below) to allow the caller to determine the state of a particular hyperlink. The values of the HLQF enumeration in the illustrated architecture 300 are shown in the following table.
| TABLE 48 |
|---|
| HLQF Enumeration Constants. |
[0802] 7.6.11 The CF_HYPERLINK Clipboard Format
[0803] The illustrated hyperlink objects 320-321 support the IPersistStream interface, and can be stored as a serialized data stream (i.e., in the well known OLE IStream object) having a CF_HYPERLINK data format using the OleSaveToStreamEx function (a well known OLE function). For OLE Uniform Data Transfer in an object supporting the well known OLE IDataObject interface, the CF_HYPERLINK format may appear in either TYMED_IStream or TYMED_HGLOBAL mediums.
[0804] 7.6.12 The HLSR Enumeration
[0805] The HLSR enumeration defines values that are passed to an HlinkGetSpecialReference and an HlinkSetSpecialReference API functions (described below) to specify which value to set or get. The values of the HLSR Enumeration in the illustrated architecture are shown in the following table.
| TABLE 49 |
|---|
| HLSR Enumeration Values. |
[0806] 7.7 Hyperlinking Architecture API Functions
[0807] 7.7.1 The HlinkCreateBrowseContext API Function
[0808] This API function creates an empty, default instance of the system's hyperlink browse context object 350, and performs the equivalent of the function call, “CoCreateInstance(CLSID_StdHlinkBrowseContext, punkOuter, CLSCTX_SERVER, riid, ppv).” The parameters and return values of the function in the illustrated architecture 300 are shown in the following table.
| TABLE 50 |
|---|
| HlinkCreateBrowseContext API Function |
| Parameters and Return Values. |
[0809] 7.7.2 The HlinkQueryCreateFromData API Function This function determines whether a hyperlink object can be created from a given IDataObject. In the illustrated hyperlink architecture 300, a hyperlink object can be created from a data storage object with the IDataObject interface if either, (1) the object offers the CF_HYPERLINK data format on either TYMED_IStream or TYMED_HGLOBAL storage mediums; or (2) the object offers data in a Windows® 95 shortcut format. The parameters and return values of the HlinkQueryCreateFromData API function in the illustrated architecture 300 are shown in the following table.
| TABLE 51 |
|---|
| HlinkQueryCreateFromData API Function |
| Parameters and Return Values |
[0810] 7.7.3 The HlinkCreateFromData API Function
[0811] This API function creates a hyperlink object (e.g., the objects 320-321) from serialized data of a hyperlink object stored in a storage object having the IDataObject interface. Typically, the IDataObject storage object originates from a data transfer operation, such as a copy-paste transfer operation using the clipboard, or a drag-and-drop operation. In the clipboard transfer case, the transfer's destination application retrieves an interface pointer of the storage object's IDataObject interface via the well known OleGetClipboard function when processing a paste command. During a drag-and-drop transfer, an interface pointer of the storage object's IDataObject interface is passed in through the well known lDropTarget::Drop function to a destination application object supporting the well known OLE IDropTarget interface which was registered (using the well known RegisterDragDrop API function) to the destination application's window over which the mouse was released during the drag operation.
[0812] Once the destination application obtains the IDataObject interface pointer, the application enumerates available formats to determine how the new data is to merge with existing data. Typically, the destination application enumerates formats in order of highest-fidelity formats (such as OLE embedding or link objects and their own native data formats), medium-fidelity transfer formats (such as CF_RTF, CF_METAFILEPICT, CF_DIB, and so on), and finally low-fidelity transfer formats (such as CF_TEXT). The actual enumeration order depends on the context of the paste or drop operation and on the application itself and its user interaction model.
[0813] The following sample pseudo-code would typically be inserted at some point in function implementing paste or drop operations to allow for pasting and dropping of hyperlinks:
[0814] if (HlinkQueryCreateFromData(pdatobj) == S_OK) {
[0815] // create a hyperlink site and other hyperlink-specific
[0816] information as needed
[0817] hr = HlinkCreateFromData(pdatobj, &hlSiteNew,
[0818] dwSiteData, NULL, IID_IHlink, (void**)&hlNew);
[0819] }
[0820] The HlinkCreateFromData API function's parameters and return values in the illustrated architecture 300 are shown in the following table.
| TABLE 52 |
|---|
| HlinkCreateFromData API Function Parameters and Return Values. |
[0821] 7.7.4 The HlinkCreateFromMoniker API Function
[0822] This API function creates a hyperlink object (e.g., hyperlink objects 320-321) from a moniker, a location string, and a friendly name. Typically, the function is used by the hyperlink container 330 as part of a user interface feature with which a user creates a new hyperlink based on an existing hyperlink, or edits an existing hyperlink. The following example demonstrates creating a new hyperlink phlNew from an existing hyperlink, phI, using the HlinkCreateFromMoniker API function by changing only the location within the hyperlink target.
[0823] phl->GetMonikerReference(&pmk, &szLocation);
[0824] phl->GetFriendlyName(&szFriendlyName);
[0825] // present Ul allowing the user to change the destination of the
[0826] hyperlink within the same hyperlink target
[0827] // show them szLocation, allow them to change it to
[0828] szLocationNew, same for szFriendlyName
[0829] HlinkCreateFromMoniker(pmk, szLocationNew,
[0830] szFriendlyNameNew, &hlSite, dwSiteData, NULL,
[0831] IID_IHlink, &phlNew);
[0832] The parameters and return values of the HlinkCreateFromMoniker API function in the illustrated architecture 300 are shown in the following table.
| TABLE 53 |
|---|
| HlinkCreaterFromMoniker API Function |
| Parameters and Return Values. |
[0833] 7.7.5 The HlinkCreateFromString API Function
[0834] This function creates a hyperlink object from text strings representing the hyperlink target, the location within the target, and a friendly name. Typically, the hyperlink container 330 uses this API function as part of a user-interface feature for creating new hyperlinks, where the user fills in a form or dialog of items, e.g., text strings for a target, location, friendly name, from which the hyperlink object is constructed. The following table shows the parameters and return values of the HlinkCreateFromString API in the illustrated architecture 300.
| TABLE 54 |
|---|
| HlinkCreateFromString API Function Parameters and |
[0835] 7.7.6 The HlinkGetSpecialReference API Function
[0836] For a given value from the HLSR enumeration, this API function returns the current user's default global home, search, or history page for browsing as a string. As an example, the browser application illustrated in FIG. 2 can use this API to retrieve a string that represents a user's home page to which the browser application navigates on launch or when executing a Go Home command. For navigating to the page, the browser application converts the string returned from the HlinkGetSpecialReference API function to a hyperlink object via the HlinkCreateFromString API function. The following table shows the parameters and return values of the HlinkGetSpecialReference API function in the illustrated hyperlinking architecture 300.
| TABLE 55 |
|---|
| HlinkGetSpecialReference API Function Parameters and |
| Return Values. |
[0837] 7.7.7 The HlinkSetSpecialReference API Function
[0838] For a given value from the HLSR enumeration, this API function sets the current user's default global home, search, or history page for browsing. For example, the browser application of FIG. 2 uses this API function to implement a Set Home command, with which the user sets the currently visible navigation point as his or her home page.
| TABLE 56 |
|---|
| The HlinkSetSpecialReference API Function Parameters |
| and Return Values. |
[0839] 7.7.8 The HlinkNavigateToStringReference API Function
[0840] This API function encapsulates the following common sequence of calls:
[0841] // create hyperlink site, IBindStatusCallback, gather bind context,
[0842] and browse context
[0843] HlinkCreateFromString(szTarget, szLocation, szFriendlyName,
[0844] &hlSite, dwSiteData, NULL, IID_IHIink, (void**)&phl);
[0845] HlinkNavigate(phl, phlFrame, grfHLNF, pbc, pbsc, phlbc);
[0846] phl->Release( );
[0847] The following table shows the parameters and return values of the HlinkNavigateToStringReference API function in the illustrated architecture 300.
| TABLE 57 |
|---|
| HlinkNavigateToStringReference API Function Parameters |
| and Return Values. |
[0848] 7.7.9 The HlinkNavigate API Function
[0849] This API function performs hyperlink navigates on a given hyperlink object and an optional hyperlink frame object. The function encapsulates the following sequence of calls:
[0850] if (phlFrame)
[0851] phlFrame->Navigate(grfHLNF, pbc, pbsc, phl);
[0852] else if (phl)
[0853] phl->Navigate(grfHLNF, pbc, pbsc, phlbc);
[0854] The following table shows the parameters and return values of the HlinkNavigate API function in the illustrated architecture 300.
| TABLE 58 |
|---|
| HlinkNavigate API Function Parameters and Return |
| Values. |
[0855] 7.7.10 The HlinkOnNavigate API Function
[0856] This API function encapsulates a sequence of steps performed in the IHlinkTarget::Navigate function (described below) of the hyperlink target object 310, namely calls to the IHlinkBrowseContext::OnNavigateHlink and IHlinkFrame::OnNavigate functions if the hyperlink target has a hyperlink frame such as the following:
[0857] phlbc->OnNavigateHlink(grfHLNF, pmkTarget, szLocation,
[0858] szFriendlyName);
[0859] if (phlframe) phlframe->OnNavigate(grfHLNF);
[0860] The following table shows the parameters and return values of the HlinkOnNavigate API function in the illustrated hyperlinking architecture 300.
| TABLE 59 |
|---|
| HlinkOnNavigate API Function Parameters and Return |
| Values. |
[0861] 7.8 The IHlinkSite Interface
[0862] The IHlinkSite interface 338 of the hyperlink site objects 334-335 exposes member functions which allow the hyperlink objects 320-321 to evaluate a hyperlink target moniker relative to the hyperlink container 330. For example, the hyperlink object uses the IHlinkSite interface functions to evaluate a relative hyperlink target moniker that references a relative URL, such as “embeddedImage.gif,” in relation to a base URL of the hyperlink container, such as “http://www.website.com/,” so as to form the full URL of the hyperlink target (“http://www.website.com/embeddedImage.gif”). The member functions of the IHlinkSite interface 338 in the illustrated architecture 300 are detailed below.
[0863] 7.8.1 The IHlinkSite::GetMoniker Function
[0864] This member function of the IHlinkSite interface 338 returns the moniker of the hyperlink container 330 for the hyperlink site 334-335. In the IHlink::Navigate function (described below), the hyperlink objects 320-321 call the IHlinkSite::GetMoniker function on the hyperlink site object 334-335 to retrieve a relative moniker designating the hyperlink container 330. The hyperlink objects use this moniker to determine if the hyperlink navigation is internal (i.e., to another location within the same hyperlink container 330, such as shown in FIG. 9 for the hyperlink object 320), or externally to another hyperlink target 310 (as shown in FIG. 9 for the hyperlink object 321). The following table shows the parameters and return values of the IHlinkSite::GetMoniker function in the illustrated architecture 300.
| TABLE 60 |
|---|
| IHlinkSite::GetMoniker Function Parameters and Return |
| Values. |
[0865] 7.8.2 The IHlinkSite::GetInterface Function
[0866] This function retrieves an interface on the hyperlink container 330 (which is usually the document that contains the hyperlink site 33-4335). Typically the IHlinkSite::GetInterface function is called by the hyperlink object 320-321 after calling the IHlinkSite::GetMoniker function and determining that there is no relative moniker as part of the hyperlink object's IHlink::Navigate function. The hyperlink object then calls the IHlinkSite::GetInterface function (with the riid parameter set to IID_IHlinkTarget) to retrieve an interface pointer of the IHlinkTarget interface 312 on the hyperlink container 330 so that the hyperlink object can directly call the hyperlink container's IHlinkTarget::Navigate function (described below), and thereby avoiding the typical moniker binding process. Accordingly, the IHlinksite::GetInterface function behaves similarly to the QueryInterface function (a well known OLE function), except that the GetInterface function may choose which interface to return based on the dwSiteData parameter. Further, the interface returned from the function is not necessarily implemented on the same object that exposes IHlinkSite. The following table shows the parameters and return values of the IHlinksite::GetInterface function.
| TABLE 61 |
|---|
| IHlinkSite::GetInterface Function Parameters and Return |
| Values. |
[0867] 7.8.3 The IHlinkSite::OnNavigationComplete Function
[0868] The hyperlink object 320-321 calls this method on the hyperlink site 334-335 to notify the hyperlink site that hyperlink navigation has been completed. The following table shows the parameters and return values of the IHlinkSite::OnNavigationComplete function in the illustrated architecture 300.
| TABLE 62 |
|---|
| IHlinkSite::OnNavigationComplete Function Parameters and |
| Return Values. |
[0869] 7.9 The IHlink Interface
[0870] The hyperlink objects 320-321 in the hyperlinking architecture 300 support the IHlink interface which exposes member functions so as to allow the container 330to set or retrieve the hyperlink object's hyperlink site, hyperlink target moniker, location string, and friendly name, as well as to initiate hyperlink navigation. These member functions are described below.
[0871] 7.9.1 The IHlink::SetHlinkSite Function
[0872] The hyperlink container 330 calls this function on the IHIink interface of the hyperlink objects 320-321 to set the hyperlink site and associated site data on the hyperlink object. The hyperlink container 330 typically constructs the hyperlink site 334-335 first and then passes it through this function to a newly constructed hyperlink object. The hyperlink object 320-321 uses the hyperlink site 334-335 in order to navigate properly (i.e., relative to the hyperlink container 330) when IHlink::Navigate is called. The HlinkCreateFromData, HlinkCreateFromMoniker, and HlinkCreateFromString API functions also encapsulate calls to this function. The following table shows the parameters and return values of the IHlink::SetHlinkSite function in the illustrated architecture 300.
| Table 63 |
|---|
| IHlink::SetHlinkSite Function Parameters and Return |
| Values. |
[0873] 7.9.2 The IHlink::GetHlinkSite Function
[0874] This function returns the hyperlink site and associated site data from the hyperlink object 320-321. The following table shows the parameters and return values of the IHlink::GetHlinkSite function in the illustrated architecture 300.
| Table 64 |
|---|
| IHlink::GetHlinkSite Function Parameters and Return |
| Values. |
[0875] 7.9.3 The IHlink::GetMonikerReference Function
[0876] This function returns the hyperlink target moniker and location string of the hyperlink object 320-321. The hyperlink container 330 or other caller of this function can use the hyperlink target moniker to bind to the hyperlink object's hyperlink target via the function call, “IMoniker::BindToObject( . . . , IID_IHlinkTarget, . . . ).” The hyperlink container 330 or other caller of this function can pass the location string to the hyperlink target via the IHlinkTarget::Navigate function (described below) to navigate to the proper destination within the target. The hyperlink container 330 also can use the location string to retrieve the current friendly name of the location within the target via the IHlinkTarget::GetFriendlyName function (described below). The following table shows the parameters and return values of the IHlink::GetMonikerReference function in the illustrated architecture 300.
| Table 65 |
|---|
| IHlink::GetMonikerReference Function Parameters and |
| Return Values. |
[0877] 7.9.4 The IHlink::GetStringReference Function
[0878] This function retrieves strings from the hyperlink object 320-321 that identify the hyperlink target and the location within the hyperlink target. The implementation of this function in the illustrated hyperlink objects 320-321 retrieves the pszTarget string by calling the IMoniker::GetDisplayName function (described above) on the hyperlink target moniker in the hyperlink object 320-321. The following table shows the parameters and return values of the IHIink::GetStringReference function in the illustrated architecture 300.
| Table 66 |
|---|
| IHlink::GetStringReference Function Parameters and |
| Return Values. |
[0879] 7.9.5 The IHlink::GetFriendlyName Function
[0880] This function retrieves the friendly name of the hyperlink object 320-321. The illustrated hyperlink objects 320-321 cache their friendly name, so the hyperlink object's friendly name may not necessarily correspond to the friendly name of the hyperlink target (which the hyperlink target returns via the IHlinkerTarget::GetFriendlyName function, described below). The illustrated hyperlink objects 320-321 update the friendly name as part of the IHlink::Navigate function (described below). The hyperlink container 330 typically calls the IHlink::GetFriendlyName function to obtain the friendly names of the hyperlink objects for use in representing the hyperlinks within the hyperlink container's user interface. The following table shows the parameters and return values of the IHlink::GetFriendlyName function in the illustrated architecture 300.
| Table 67 |
|---|
| IHlink::GetFriendlyName Function Parameters and Return |
| Values. |
[0881] 7.9.6 The IHlink::SetFriendlyName Function
[0882] This function sets the friendly name of the hyperlink object 320-321. The following table shows the parameters and return values of the IHlink::SetFriendlyName function in the illustrated architecture 300.
| Table 68 |
|---|
| IHlink::SetFriendlyName Function Parameters and Return |
| Values. |
[0883] 7.9.7 The IHlink::GetTargetFrameName Function
[0884] This function retrieves the name of the hyperlink frame 340-341 for the hyperlink object's hyperlink target. The following table shows the parameters and return values of the IHlink::GetTargetFrameName function in the illustrated architecture 300.
| TABLE 69 |
|---|
| IHlink::GetTargetFrameName Function Parameters and |
| Return Values. |
[0885] 7.9.8 The IHlink::SetTargetFrameName Function
[0886] This funtion sets the target frame name for the hyperlink object 320-321. In the illustrated architecture 300, the target frame name is a text string that names the target frame 340-341 in which the hyperlink navigation is to occur, as an HTML frame-set. The following table shows the parameters and return values of the illustrated IHlink::SetTargetFrameName function.
| TABLE 70 |
|---|
| IHlink::SetTargetFrameName Function Parameters and |
| Return Values. |
[0887] 7.9.9 The IHlink::GetAdditionalParams Function
[0888] This function retrieves additional properties of the hyperlink object 320-321. The illustrated hyperlink objects 320-321 represent these properties as a parameter string having an extensible format as follows:
[0889] <ID1=“value1”> <ID2=“value2”> . . . <Idn=“valuen”>
[0890] The parameters saved in this string are interpreted mainly by the hyperlink frame 340-341. The following table shows the parameters and return values of the IHlink::GetAdditionalParams function in the illustrated architecture 300.
| TABLE 71 |
|---|
| IHlink::GetAdditionalParams Function Parameters and |
| Return Values. |
[0891] 7.9.10 The IHlink::SetAdditionalParams Function
[0892] This function sets the additional parameters string of the hyperlink objects 320-321. The following table shows the parameters and return values of the IHlink::SetAdditionalParams function in the illustrated architecture 300.
| TABLE 72 |
|---|
| IHlink::SetAdditionalParams Function Parameters and |
| Return Values. |
[0893] 7.9.11 The IHlink::Navigate Function
[0894] The hyperlink container call this funtion to initiate hyperlink navigation by the hyperlink object 320-321 as described above. The following table shows the parameters and return values of the IHlink::Navigate function in the illustrated architecture 300.
| TABLE 73 |
|---|
| IHlink::Navigate Function Parameters and Return Values. |
[0895] 7.9.12 The IHlink::GetMiscStatus Function
[0896] The hyperlink container 330 (or other caller) calls this function to query whether the hyperlink represented by the hyperlink object 320-321 is an absolute or a relative hyperlink. The following table shows the parameters and return values of the IHIink::GetMiscStatus function in the illustrated architecture 300.
| TABLE 74 |
|---|
| IHlink::GetMiscStatus Function Parameter and Return |
| Values. |
[0897] 7.10 The IHlinkTarget Interface
[0898] Hyperlink targets 310, 330 implement the IHlinkTarget interface 312 to allow navigation to locations within the hyperlink targets. The following hyperlink target class definition shows the implementation of the illustrated hyperlink targets 310, 330 which maintains values to track the current hyperlinking browse context 350.
| class CHlinkTarget: public IHlinkTarget { |
[0899] 7.10.1 The IHlinkTarget::SetBrowseContext Function
[0900] This function establishes the current hyperlink browse context 350 for the hyperlink target 310, 330. The illustrated hyperlink targets 310, 330 track only one browse context at a time, and release any references to prior browse contexts when a new hyperlink browse context is established via this function (as shown in the example pseudo-code for step 460 of FIG. 11). In this function, the hyperlink targets also register themselves with the established browse context 350. Later, during hyperlink navigation, the hyperlink target notifies the established hyperlink browse context 350 of a navigation event in the IHlinkTarget::Navigate function (described below) by calling the IHlinkBrowseContext::OnNavigateHlink function (described below) on the browse context. Hyperlink targets which utilize the simple hyperlink navigation process 400 shown in FIG. 10 can implement this function as a stub function which returns the value, E_NOTIMPL, when called. The following table shows the parameters and return values of the IHlinkerTarget::SetBrowseContext function in the illustrated architecture 300.
| TABLE 75 |
|---|
| IHlinkTarget::SetBrowseContext Function Parameters and |
| Return Values. |
[0901] 7.10.2 The IHlinkTarget::GetBrowseContext Function
[0902] This function retrieves the currently established browse context 350 of the hyperlink target 310, 330. The following pseudo-code example demonstrates the implementation of this method by the illustrated hyperlink target 310 holding a reference to its browse context:
[0903] CHlinkTarget::GetBrowseContext(IHlinkBrowseContext** pphlbc)
[0904] {
[0905] *pphlbc = m_phlbc;
[0906] if (m_phlbc)
[0907] m_phlbc->AddRef( );
[0908] return S_OK;
[0909] } // CHlinkTarget::GetBrowseContext
[0910] Hyperlink targets which utilize only the simple hyperlink navigation process 400 shown in FIG. 10 can implement this function as a stub function which returns the value, E_NOTIMPL, when called. The following table shows the parameter and return values of the IHlinkTarget::GetBrowseContext function in the illustrated architecture 300.
| TABLE 76 |
|---|
| IHlinkTarget::GetBrowseContext Function Parameter and |
| Return Values. |
[0911] 7.10.3 The IHlinkTarget::Navigate Function
[0912] As described above, the hyperlink object 320-321 calls this function during the hyperlink navigation process 450 of FIG. 11 to cause the hyperlink target to navigate to a specified location (i.e., the location designated by the location string of the hyperlink target). If the specified location (i.e., the szLocation parameter) is not visible, the function navigates to and shows that location within the hyperlink target (as in the example pseudo-code shown above for the step 462 of FIG. 11).
[0913] Hyperlink targets which utilize only the simple hyperlink navigation process 400 shown in FIG. 10 implement this function, but do not utilize the browse context for window position information. The following table shows the parameter and return values of the IHlinkTarget::Navigate function in the illustrated architecture 300.
| TABLE 77 |
|---|
| IHlinkTarget::Navigate Function Parameters and Return |
| Values. |
[0914] 7.10.4 The IHlinkTarget::GetMoniker Function
[0915] This function returns a moniker which references the hyperlink target 310, 330 for a given location within the hyperlink target specified by an input parameter, szLocation. The following pseudo-code example shows the implementation of the IHlinkTarget::GetMoniker function in the illustrated hyperlink target 310.
[0916] CHlinkTarget::GetMoniker(LPCWSTR sz:location, DWORD
[0917] dwAssign, IMoniker** ppmk)
[0918] {
[0919] // possibly create moniker dynamically according to
[0920] dwAssign, simple targets will keep one on hand
[0921] *ppmk = m_pmk;
[0922] if (m_pmk)
[0923] m_pmk->AddRef( );
[0924] return S_OK;
[0925] } // CHlinkTarget::GetMoniker
[0926] The following table shows the parameters and return values of the IHlinkerTarget::GetMoniker function in the illustrated architecture 300.
| TABLE 78 |
|---|
| IHlinkTarget::GetMoniker Function Parameters and Return |
| Values. |
[0927] 7.10.5 The IHlinkTarget::GetFriendlyName Function
[0928] This function returns a friendly name for the location within the hyperlink target specified by the input parameter, szLocation. The following table shows the parameters and return values of the IHlinkTarget::GetFriendlyName function in the illustrated architecture 300.
| TABLE 79 |
|---|
| IHlinkTarget::GetFriendlyName Function Parameters and |
| Return Values. |
[0929] 7.11 The IHlinkFrame Interface
[0930] The hyperlink frames 340-341 expose functions through the IHlinkFrame interface 342 to integrate with the hyperlink browse context 350. This integration allows the hyperlink frame 341 which hosts the hyperlink target 310 to properly position its window to create the appearance of window reuse when navigating to the hyperlink target. Hyperlink frames which utilize only the simple hyperlink navigation process shown in FIG. 10 need not integrate with the hyperlink browse context 350.
[0931] 7.11.1 The IHlinkFrame::SetBrowseContext Function
[0932] This function sets the hyperlink browse context 350 of the hyperlink frame 340-341. Hyperlink frames which utilize only the simple hyperlink navigation process 400 shown in FIG. 10 can implement this function as a stub function which returns the value, E_NOTIMPL, when called. The following table shows the parameter and return values of the IHlinkFrame:: SetBrowseContext function in the illustrated architecture 300.
| TABLE 80 |
|---|
| IHlinkFrame::SetBrowseContext Function Parameters and |
| Return Values. |
[0933] 7.11.2 The IHlinkFrame::GetBrowseContext Function
[0934] This function returns the browse context of the hyperlink frame 340-341. Hyperlink frames which utilize only the simple hyperlink navigation process 400 shown in FIG. 10 can implement this function as a stub function which returns the value, E_NOTIMPL, when called. The following table shows the parameter and return values of the IHlinkFrame::GetBrowseContext function in the illustrated architecture 300.
| TABLE 81 |
|---|
| IHlinkFrame::GetBrowseContext Function Parameters and |
| Return Values. |
[0935] 7.11.3 The IHlinkFrame::Navigate Function
[0936] This function initiates hyperlink navigation by a hyperlink object specified by its phylNavigate parameter. As described above for the simple hyperlink navigation process 400 of FIG. 10 and the full hyperlink navigation process of FIG. 11, the IHlinkFrame::Navigate function is typically called by the hyperlink object 320-321 in the hyperlink object's IHlink::Navigate function to allow the hyperlink frame to interpose itself in the hyperlink navigation process. The following table shows the parameters and return values of the IHlinkFrame::Navigate function in the illustrated architecture.
| TABLE 82 |
|---|
| IHlinkFrame::Navigate Function Parameters and Return |
| Values. |
[0937] 7.11.4 The IHlinkFrame::OnNavigate Function
[0938] The hyperlink target 310 calls this function Qn its hyperlink frame 341 during the IHlinkerTarget::Navigate function (described above), usually via the HlinkOnNavigate API Function (described above), to notify the hyperlink frame that a hyperlink has been navigated. This allows the hyperlink frame to update user interface elements associated with navigation. The following table shows the parameters and return values of the IHlinkFrame::OnNavigate function in the illustrated architecture 300.
| TABLE 83 |
|---|
| IHlinkFrame::OnNavigate Function Parameters and Return |
| Values. |
[0939] 7.12 The IHIinkBrowseContext Interface
[0940] The hyperlink browse context 350 exposes functions through the IHlinkBrowseContext interface which allow objects that integrate with the browse context (e.g., the hyperlink objects, hyperlink containers, hyperlink targets, and hyperlink frames) to register and retrieve information relating to hyperlink navigation. This allows the browse context 350 to maintain the navigation stack, which is utilized for “go back” and “go forward” commands. These functions also provide for exchanging window position information (including hyperlink navigation toolbar position) between the hyperlink frame 340 of the hyperlink container 330 and the hyperlink frame 341 of the hyperlink target 310 to create the appearance of window reuse.
[0941] 7.12.1 The IHlinkBrowseContext::Register Function
[0942] This function registers a calling object (e.g., the hyperlink target 310) with the browse context 350. The browse context 350 maintains a table of moniker-object bindings (the running objects table 358 of FIG. 9) to facilitate reuse of hyperlink targets during navigation. When navigating to a hyperlink target, the hyperlink object 320-321 consults this table (via an IHlinkBrowseContext::GetObject function described below) to check whether the hyperlink target 310 is already registered as running, and thus avoid launching a new instance of the hyperlink target application and reloading the already running hyperlink target.
[0943] In the illustrated architecture 300, each hyperlink target 310 is required to register in the browse context 350 using the IHlinkBrowseContext::Register function when their IHlinkerTarget::SetBrowseContext function is called. The hyperlink target 310 keeps the value returned through the output parameter, *pdwRegister, for use in revoking the registration. The hyperlink target unregisters from the browse context 350 (by calling an IHlinkBrowseContext::Revoke function described below) on shutdown or if their established browse context changes (from a call to the IHlinkTarget::SetBrowseContext function described above).
[0944] The following table shows the parameters and return values of the IHlinkBrowseContext:: Register function in the illustrated architecture 300.
| TABLE 84 |
|---|
| IHlinkBrowseContext::Register Function Parameters and |
| Return Values. |
[0945] 7.12.2 The IHlinkBrowseContext::GetObject Function
[0946] This function retrieves an object previously registered in the browse context under the name specified by a parameter, pmk. The following table shows the parameters and return values of the IHlinkBrowseContext::GetObject function in the illustrated architecture 300.
| TABLE 85 |
|---|
| IHlinkBrowseContext::GetObject Function Parameters and |
| Return Values. |
[0947] 7.12.3 The IHlinkBrowseContext::Revoke Function
[0948] This function revokes a registration of an object with this browse context previously made using the IHlinkBrowseContext::Register function described above. The following table shows the parameters and return values of the IHlinkBrowseContext::Revoke function in the illustrated architecture 300.
| TABLE 86 |
|---|
| IHlinkBrowseContext::Revoke Function Parameters and |
| Return Values. |
[0949] 7.12.4 The IHlinkBrowseContext::SetBrowseWindowInfo Function
[0950] This function establishes the HLBWINFO structure (described above) of the browse context 350. The HLBWINFO structure contains information about the position and properties of the document- and frame-level windows of other hyperlink frames and documents which use the browse context 350. The hyperlink targets and containers 310, 330 call this function whenever their document-level (and optionally their frame-level) user interface is resized. This occurs under the Windows® operating system for example, if the user moves their document window, tiles several frame-level applications, or moves the task-bar and causes their windows to receive WM_SIZE, WM_MOVE, or WM_WINDOWPOSCHANGED messages (which are well known window messages in the Windows®) operating system). The following table shows the parameters and return values of the IHlinkBrowseContext::SetBrowseWindowInfo function in the illustrated architecture 300.
| TABLE 87 |
|---|
| IHlinkBrowseContext::SetBrowseWindowInfo Function |
| Parameters and Return Values. |
[0951] 7.12.5 The IHlinkBrowseContext::GetBrowseWindowInfo Function
[0952] This function retrieves the HLBWINFO structure (described above) currently associated with the browse context 350. The following table shows the parameters and return values of the IHIinkBrowseContext::GetBrowseWindowInfo function in the illustrated architecture 300.
| TABLE 87 |
|---|
| IHlinkBrowseContext::GetBrowseWindowInfo Function |
| Parameters and Return Values. |
[0953] 7.12.6 The IHlinkBrowseContext::EnumNavigationStack Function
[0954] This function returns an enumerator function pointer which can be used to enumerate the current contents of the navigation stack. The enumerator returns HLITEM structures (a well known OLE data, structure), which contain references to the previously navigated hyperlinks recorded in the navigation stack (in the form of HLID values described above), and “friendly names” which can be displayed in a user interface. The hyperlink frame 340-341 typically calls this function when presenting drop-down lists and dialog boxes for a history list or like browsing feature. The following table shows the parameters and return values of the IHlinkBrowseContext::EnumNavigationStack function in the illustrated architecture 300.
| TABLE 88 |
|---|
| IHlinkBrowseContext::EnumNavigationStack Function |
| Parameters and Return Values. |
[0955] 7.12.7 The IHlinkBrowseContext::QueryHlink Function
[0956] This function tests the validity of an HLID value (described above). This function is typically called by user interface elements of the hyperlink frame 340-341 to determine whether or not to enable features such as “Go Forward” and “Go Back” commands by passing the HLID values, HLID_NEXT and HLID_PREVIOUS, as the uHLID of the function, as in the following pseudo code example:
[0957] // tests if Go Forward should be enabled
[0958] phlbc->QueryHlink(HLQF_ISVALID, HLID_NEXT);
[0959] // tests if Go Back should be enabled
[0960] phlbc->QueryHlink(HLQF_ISVALID, HLID_PREVIOUS);
[0961] The following table shows the parameters and return values of the IHlinkBrowseContext::QueryHlink function in the illustrated architecture 300.
| TABLE 89 |
|---|
| IHlinkBrowseContext:: QueryHlink Function Parameters and |
| Return Values. |
[0962] 7.12.8 The IHlinkBrowseContext::GetHlink Function
[0963] This function retrieves a hyperlink from the browse context 350 specified by an HLID constant (described above). The following table shows the parameters and return values of the IHlinkBrowseContext::GetHlink function in the illustrated architecture 300.
| TABLE 90 |
|---|
| IHlinkBrowseContext::GetHlink Function Parameters and |
| Return Values. |
[0964] 7.12.10 The IHlinkBrowseContext::SetCurrentHlink Function
[0965] This function sets the current hyperlink in the navigation stack of the browse context 350. The following table shows the parameters and return values of the IHlinkBrowseContext::SetCurrentHlink function in the illustrated architecture 300.
| TABLE 91 |
|---|
| IHlinkBrowseContext::SetCurrentHlink Function Parameters |
| and Return Values. |
[0966] 7.12.10 The IHinkBrowseContext::OnNavigateHlink Function
[0967] The hyperlink target 310 calls this function (as part of the IHinkTarget::Navigate function described above) to notify the browse context 350 that a hyperlink has been successfully navigated (i.e., at the step 465 of the full hyperlink navigation process 450 of FIG. 11). The following table shows the parameters and return values of the IHlinkBrowseContext::OnNavigateHlink function in the illustrated architecture 300.
| TABLE 92 |
|---|
| IHlinkBrowseContext::OnNavigateHlink Function |
| Parameters and Return Values. |
[0968] 7.12.11 The IHlinkBrowseContext::Clone Function
[0969] This function creates a duplicate of the browse context 350. The following table shows the parameters and return values of the IHlinkBrowseContext::Clone function in the illustrated architecture 300.
| TABLE 93 |
|---|
| IHlinkBrowseContext::Clone Function Parameters and |
| Return Values. |
[0970] 7.18.12 The IHlinkBrowseContext::Close Function
[0971] This function closes the hyperlink browse context, and releases all hyperlink targets that have been registered with the browse context via IHlinkBrowseContext::Register. The following table shows the parameters and return values of the IHlinkBrowseContext::Close function in the illustrated architecture 300.
| TABLE 94 |
|---|
| IHlinkBrowseContext::Close Function Parameters and |
| Return Values. |
[0972] Having described and illustrated the principles of our invention with reference to an illustrated embodiment, it will be recognized that the illustrated embodiment can be modified in arrangement and detail without departing from such principles. It should be understood that the programs, processes, or methods described herein are not related or limited to any particular type of computer apparatus, unless indicated otherwise. Various types of general purpose or specialized computer apparatus may be used with or perform operations in accordance with the teachings described herein. Elements of the illustrated embodiment shown in software may be implemented in hardware and vice versa.
[0973] In view of the many possible embodiments to which the principles of our invention may be applied, it should be recognized that the detailed embodiments are illustrative only and should not be taken as limiting the scope of our invention. Rather, we claim as our invention all such embodiments as may come within the scope and spirit of the following claims and equivalents thereto.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
We claim:
1. A method of computer software execution supporting browsing documents of a plurality of different application programs in a computer system, each application program implementing a document object server which provides document objects to encapsulate data of documents of a type associated with the application program together with operational code to display views of the documents, the document objects individually supporting a document object interface for use by a frame object to cause the operational code of the document objects to display their respective document's display view within a designated display area framed within an application window frame managed by the respective frame object, wherein an object used in the method is a programming entity that encapsulates data members to provide storage of data with function members implemented by operational code to provide processing of the data and that has an interface exposing the function members to programmatic access by a client program, the method comprising:
providing a frame object having operational code for managing a frame displayed within a window and having a document display area, and for interacting with any document object hosted by the frame object through the document object interface to cause such hosted document object to display a display view of a document encapsulated by the hosted document object within the document display area;
creating a first document object to encapsulate data of a first document using an object server of a first application program associated with a type of the first document, the first document containing a hyperlink to a second document of a type associated with a second different application program;
causing the frame object to host the first document object with the first document object displaying a view of the first document in the document display area;
creating a second document object to encapsulate data of the second document using an object server of the second application; and
on activation of the hyperlink by a user, causing the frame object to host the second document object with the second document object displaying a view of the second document in place of the view of the first document in the document display area;
wherein a user can activate the hyperlink within the display area containing the view of the first document, said view controlled by the first document object created using the object server of the first application, said activation thereby causing the frame object to host within the display area the view of the second document, said view controlled by the second document object created using the object server of the second application.
2. A hyperlink navigation system for unified browsing of documents from multiple applications a plurality of different application programs in a computer, wherein an object of the hyperlink navigation system is a programming entity that encapsulates data members to provide storage of data with function members implemented by operational code to provide processing of the data and that has an interface exposing the function members to programmatic access by a client program, the hyperlink navigation system comprising:
a first object server application program for providing an instance of a hyperlink container object, the hyperlink container object encapsulating data of a container document containing a hyperlink together with operational code to display a view of the container document;
a second different object server application program for providing an instance of a hyperlink target object, the hyperlink target object encapsulating data of a target document indicated by the hyperlink together with operational code to display a view of the target document;
a frame object for hosting one of the hyperlink container object and the hyperlink target object and for managing a frame having a display area in which the hosted object displays its respective view; and
a hyperlink navigation system object server for providing an instance of a hyperlink object to be used with the hyperlink container object and operative to navigate the hyperlink by causing the frame object to change from hosting the hyperlink container object to hosting the hyperlink target object;
wherein a user can activate the hyperlink within the display area containing the view of the container document, said view controlled by the instance of the hyperlink container object provided by the first object server application program, said activation thereby causing the frame object to host within the display area the view of the target document, said view controlled by the instance of the hyperlink target object provided by the second different object server application program.
3. The hyperlink navigation system of claim 2 wherein the hyperlink object comprises:
a moniker object containing a reference to the target document and operating to bind the target document into the hyperlink target object.
4. The hyperlink navigation system of claim 3 wherein the hyperlink object further comprises:
a text string designating a location in the target document; and
the hyperlink object operating to cause the hyperlink target object to display the location in the view of the target document.
5. The hyperlink navigation system of claim 2 comprising:
a browse context object for maintaining a navigation history of previously navigated hyperlink target documents and operating to add the target document to the navigation history when navigated by the hyperlink object.
6. Software stored on a computer readable medium for hyperlink navigation of a plurality of different application programs, wherein an object of the software is a programming entity that encapsulates data members to provide storage of data with function members implemented by operational code to provide processing of the data and that has an interface exposing the function members to programmatic access by a client program, the software comprising:
hyperlink navigation system code for creating a hyperlink object for navigating to a location in a hyperlink target, the hyperlink object having a moniker for referencing the hyperlink target, a location string for designating the location, and a navigate function for causing the moniker to bind the hyperlink target into a hyperlink target object and for causing the hyperlink target object to display a view of the hyperlink target at the location;
hyperlink navigation system code for creating a browse context object for maintaining a navigation stack to track which hyperlink targets have been navigated, said navigation stack comprising hyperlink targets of plural different application programs.
7. The software of claim 6 comprising:
an application programming interface of a function for creating the hyperlink object, calling the navigation function, and registering the hyperlink target in the navigation stack of the browse context object when navigated, the application programming interface being accessible to invocation by a client application program.
8. The software of claim 6 wherein the browse context object also passes a window position of a frame for a hyperlink container document to a frame for the hyperlink target.
Patent Citations (77)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4514800(A) | 1985-04-01 | Gruner et al. | Applicant |
| US4674040(A) | 1987-06-01 | Barker et al. | Applicant |
| US4739477(A) | 1988-04-01 | Barker et al. | Applicant |
| US4815029(A) | 1989-03-01 | Barker et al. | Applicant |
| US4933880(A) | 1990-06-01 | Borgendale et al. | Applicant |
| US4962475(A) | 1990-10-01 | Hernandez et al. | Applicant |
| US5072412(A) | 1991-12-01 | Henderson, Jr. et al. | Applicant |
| US5187786(A) | 1993-02-01 | Densmore et al. | Applicant |
| US5191645(A) | 1993-03-01 | Carlucci et al. | Applicant |
| US5204947(A) | 1993-04-01 | Bernstein et al. | Applicant |
| US5206951(A) | 1993-04-01 | Khoyi | Applicant |
| US5237680(A) | 1993-08-01 | Adams et al. | Applicant |
| US5249275(A) | 1993-09-01 | Srivastava | Applicant |
| US5274803(A) | 1993-12-01 | Dubin et al. | Applicant |
| US5297249(A) | 1994-03-01 | Bernstein et al. | Examiner |
| US5297283(A) | 1994-03-01 | Kelly, Jr. et al. | Applicant |
| US5313646(A) | 1994-05-01 | Hendricks et al. | Applicant |
| US5333317(A) | 1994-07-01 | Dann | Applicant |
| US5339423(A) | 1994-08-01 | Beitel et al. | Applicant |
| US5339424(A) | 1994-08-01 | Fushimi | Applicant |
| US5341478(A) | 1994-08-01 | Travis, Jr. et al. | Applicant |
| US5369766(A) | 1994-11-01 | Nakano et al. | Applicant |
| US5369778(A) | 1994-11-01 | San Soucie et al. | Applicant |
| US5377323(A) | 1994-12-01 | Vasudevan | Applicant |
| US5381547(A) | 1995-01-01 | Flug et al. | Applicant |
| US5408665(A) | 1995-04-01 | Fitzgerald | Applicant |
| US5410688(A) | 1995-04-01 | Williams et al. | Applicant |
| US5434975(A) | 1995-07-01 | Allen | Applicant |
| US5440744(A) | 1995-08-01 | Jacobson et al. | Applicant |
| US5446842(A) | 1995-08-01 | Schaeffer et al. | Applicant |
| US5459865(A) | 1995-10-01 | Heninger et al. | Applicant |
| US5481722(A) | 1996-01-01 | Skinner | Applicant |
| US5504898(A) | 1996-04-01 | Klein | Applicant |
| US5517655(A) | 1996-05-01 | Collins et al. | Applicant |
| US5535389(A) | 1996-07-01 | Elder et al. | Applicant |
| US5542070(A) | 1996-07-01 | LeBlanc et al. | Applicant |
| US5550976(A) | 1996-08-01 | Henderson et al. | Applicant |
| US5551035(A) | 1996-08-01 | Arnold et al. | Applicant |
| US5572643(A) | 1996-11-01 | Judson | Examiner |
| US5577252(A) | 1996-11-01 | Nelson et al. | Applicant |
| US5581686(A) | 1996-12-01 | Koppolu et al. | Applicant |
| US5581760(A) | 1996-12-01 | Atkinson et al. | Applicant |
| US5608720(A) | 1997-03-01 | Biegal et al. | Applicant |
| US5634121(A) | 1997-05-01 | Tracz et al. | Examiner |
| US5640544(A) | 1997-06-01 | Onodera et al. | Examiner |
| US5659729(A) | 1997-08-01 | Nielsen | Examiner |
| US5664178(A) | 1997-09-01 | Sinofsky | Applicant |
| US5682536(A) | 1997-10-01 | Atkinson et al. | Applicant |
| US5689703(A) | 1997-11-01 | Atkinson et al. | Applicant |
| US5706501(A) | 1998-01-01 | Horikiri et al. | Applicant |
| US5740439(A) | 1998-04-01 | Atkinson et al. | Applicant |
| US5745683(A) | 1998-04-01 | Lee et al. | Applicant |
| US5758184(A) | 1998-05-01 | Lukovsky et al. | Applicant |
| US5758358(A) | 1998-05-01 | Ebbo | Applicant |
| US5761683(A) | 1998-06-01 | Logan et al. | Examiner |
| US5764984(A) | 1998-06-01 | Loucks | Applicant |
| US5778372(A) | 1998-07-01 | Cordell et al. | Examiner |
| US5784555(A) | 1998-07-01 | Stone | Applicant |
| US5802304(A) | 1998-09-01 | Stone | Applicant |
| US5815830(A) | 1998-09-01 | Anthony | Examiner |
| US5838906(A) | 1998-11-01 | Doyle et al. | Applicant |
| US5842018(A) | 1998-11-01 | Atkinson et al. | Applicant |
| US5854630(A) | 1998-12-01 | Nielsen | Examiner |
| US5963964(A) | 1998-12-01 | Nielsen | Examiner |
| US5987480(A) | 1999-11-01 | Donohue et al. | Examiner |
| US6016520(A) | 2000-01-01 | Facq et al. | Applicant |
| US6026379(A) | 2000-02-01 | Haller et al. | Examiner |
| US6026416(A) | 2000-02-01 | Kanerva et al. | Applicant |
| US6031989(A) | 2000-02-01 | Cordell | Examiner |
| US6044205(A) | 2000-03-01 | Reed et al. | Examiner |
| US6072870(A) | 2000-06-01 | Nguyen et al. | Examiner |
| US6078326(A) | 2000-06-01 | Kilmer et al. | Examiner |
| US6098081(A) | 2000-08-01 | Heidorn et al. | Examiner |
| US6108637(A) | 2000-08-01 | Blumenau | Examiner |
| US6163772(A) | 2000-12-01 | Kramer et al. | Examiner |
| US6235027(B1) | 2001-06-01 | Weber et al. | Examiner |
| JP3191429 | 1991-08-01 | Applicant |
Non-Patent Literature (19)
- Staneck, W.R., Purcell, L. et al., “Electronic Publishing Unleased”, Chapter 22, pp. 510-542, 1995.Applicant
- Frank M. Carrano, Data Abstraction and Problem Solving with C ++, Addison-Wesley Publishing Company, pp. 14-16, 1995.Applicant
- Peterson, Baird, “Unix Variants”, Unix Review, 10(4):29-31, Apr. 1992.Applicant
- Pike, Rob et al., “UNIX—The Legend Evolves,” Plan 9 from Bell Labs, Proceedings of the Summer 1990 UKUUG Conference Jul. 9-13, 1990, Royal Lancaster Hotel, London, UK, ISBN: 0 9513181 7 9.Applicant
- Pike, Rob et al., “The Use of Name Spaces in Plan 9”, Operating Systems Review, 27(2):72-76, Apr. 1993, ISSN: 0163-5980.Applicant
- NeXTSTEP General reference, vol. 1, NeXTSTEP Publications, Addison Wesley Publishing Co., 1992, pp. 1-3 to 1-37, 2-5 to 2-16, 2-390 to 2-419, 2-503 to 2-507, 2-895 to 2-896, 2-986 to 2-987, 2-1045 to 2-1046.Applicant
- Clapp, Doug, “The NeXT Application Kit, Part I: Non-Responsive Classes,” The NeXT Bible, Brady Books, N.Y., 1990, pp. 275-280.Applicant
- Zdonik, Stanley B., “Object Management System Concepts,” Association for Computing Machinery. ACM # ACM 0-89791-1407/84/006/0013, 1984.Applicant
- Zdonik, Stanley Benjamin, Jr., “Object Management System Concepts: Supporting Integrated Office Workstation Applications,” Doctoral Thesis, Massachusetts Institute of Technology, 1983.Applicant
- Wolfgang, Herzner et al., “CDAM-Compound Document Access and Management. An Object-Oriented Approach.” Multimedia Systems, Interaction and Applications, Eurographics Workshop, Apr. 1991, Stockholm, Sweden, pp. 17-36.Applicant
- Kobayashi, Masaaki et al., “An Update on BTRON-specification OS Development,” IEEE Proceedings of the 8th Tron Project Symposium, Cat. Nr. 91THO412-7, Nov. 1991, Tokyo, Japan, pp. 132-140.Applicant
- IBM, “Creating In-Line Objects Within an Integrated Editing Environment,” IBM Technical Disclosure Bulletin, 27(5):2962, Oct. 1984.Applicant
- DiLascia, Paul et al., “Sweeper,” Microsoft Interactive Developer, vol. 1, No. 1, Spring 1996, pp. 16-52.Applicant
- Trupin, Joshua, The Visual Programmer Puts ActiveX Document Objects Through Their Paces:, Systems Journal, Jun. 1996.Applicant
- Getting Results with Microsoft Office for Windows 95, pp. 109-112, Microsoft Corporation (1996).Applicant
- Mark R. Brown, Using Netscape 2, pp. 162, 163, 148-156, 718-719, 1993.Applicant
- Elinor Mills, Navigator ‘cookies’ files will monitor Web user activity, Feb. 26, 1996.Applicant
- Al Berg, Cookies nibble at your disk drive, Jul. 8, 1996.Applicant
- Naming and Binding: Monikers, Kraig Brockschmidt, Inside Ole, Second Ed., Microsoft Press, Chap. 9, pp. 431-490, 1995.Applicant