| Title of Invention | NETWORK-BASED SOFTWARE EXTENSIONS |
|---|---|
| Abstract | A method for delivering software via a network comprising: describing (1502) one or more software extensions using descriptions that have an open schema, the extensions being configured for incorporation in a software platform executing on a client (100, 130); delivering (1510) the descriptions of the one or more extensions to the client via the network, the descriptions being configured for use in downloading the software extensions via the network; and streaming (1412, 1512) extension files to the client and enabling a user to begin interacting with an associated application program sooner than the time needed for the entire application program to load. |
| Full Text | FORM 2 THE PATENTS ACT 1970 [39 OF 1970] COMPLETE SPECIFICATION [See Section 10] "NETWORK-BASED SOFTWARE EXTENSIONS" MICROSOFT CORPORATION, a corporation of the State of Washington, which has a principal place of business at One Microsoft Way, Redmond, Washington 98052, United States of America, The following specification particularly describes the nature of the invention and the manner in which it is to be performed:- ORIGINAL 01793/MUM/2002 GRANTED 13/02/200202 TECHNICAL FIELD This invention relates to methods and systems for providing software via a network. More specifically, the invention pertains to Internet-based delivery of software. BACKGROUND OF THE INVENTION Installation of traditional PC applications requires physical media, such as a disk or CD-ROM that must be physically inserted into a computer in order for software to be loaded onto a user's computer. Typically, this process requires the user to enter settings information that can be confusing to the user. Once the software is installed, it is typically fixed in terms of its location and functionality. When the software is updated, the user must typically purchase additional physical media and repeat the installation process so that they can use the updated software. In this model, the software is fixed in its association with the computer on which it was installed. If a user moves to another computer, they will not be able to use the specific software on their machine without repeating the installation process. As computing continues to evolve into the environment of computer networks such as the Internet, it has become clear that the traditional software delivery model described above is inadequate to meet the demands of consumers who desire dynamic, flexible, and adaptable software on-demand. Network-based software delivery is becoming the subject of increasing focus by those who develop and deliver software. Unlocking the potential for network-based software delivery will require smart, innovative and streamlined solutions, especially in situations where bandwidth may be limited. Accordingly, this invention arose out of concerns associated with providing new software delivery models that are particularly well-suited for network-based software delivery, e.g. delivery via the Internet. SUMMARY OF THE INVENTION Methods and systems for network-based software delivery are described. In one embodiment, an application program or software platform resides on a client The program or platform is configured so that it is extensible based on software extensions mat are deliverable over a network such as the Internet Various extensions can be developed by third party developers for incorporation into the program or platform. In one described embodiment, extension files that comprise a software extension are hosted on a network server such as an Internet server. These include descriptor files that describe aspects of the software extension. These descriptor files logically describe an extension to the program or platform and designate the location of other extension files. Extensions are incorporated on a client by navigating to a particular network or Internet site through which the extensions can be accessed. The files describing the extension files are downloaded on the client These files tell the client where, when and how the particular extension can be plugged into the program or platform, as well as where to find the appropriate extension files and how to download them. The extension files are then downloaded and incorporated into the platform. In one embodiment, an inventive software architecture is provided for handling and consolidating particular types of descriptive files associated with various extensions. A filtering mechanism called attachment points, is used to create handlers for me different descriptive types of files that define a software extension. Each of these handlers is known as an attachment manager. Attachment managers are provided for each extensible feature type. The attachment managers interpret data from extensions files which are supplied by attachment points. In addition to predefined attachment managers, custom attachment managers can be created using data from attachment points. When an extension extends a particular feature type, the attachment points ensure that only the appropriate attachment manager is notified so that the feature type can be incorporated into the program or platform efficiently. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a high level view of a system that can be utilized in accordance with one described embodiment. Fig. 2 is an exemplary computer system that can be utilized in accordance with me described embodiment Fig. 3 is a diagram of an exemplary EDF and PKG in accordance with one described embodiment. Fig. 4 shows a portion of an EDF in accordance with the described embodiment Fig. 5 shows a portion of an EDF schema in accordance with the described embodiment Fig. 6 shows a portion of a PKG in accordance with the described embodiment Fig. 7 is a block diagram illustrating how file hashes can be used for versioning in accordance with one embodiment. Fig. 8 is a block diagram that illustrates two exemplary package objects in accordance with one embodiment. Fig. 9 is a flow diagram that describes steps in a method in accordance with one described embodiment. Fig. 10 is a flow diagram that describes steps in a method in accordance with one described embodiment Fig. 11 is a block diagram that illustrates an exemplary package manifest creation tool in accordance with one described embodiment. Fig. 12 is a flow diagram that describes steps in a method in accordance with one described embodiment Fig. 13 is a flow diagram that describes steps in a method in accordance with one described embodiment Fig. 14 is a flow diagram of steps in a method in accordance with the described embodiment. Fig. 15 is a flow diagram of steps in a method in accordance with the described embodiment. Fig. 16 shows a portion of an exemplary catalog structure in. accordance with the described embodiment. Fig. 17 is a block diagram of a software architecture in accordance with the described embodiment Fig. 18 is a flow diagram of steps in a method in accordance with the described embodiment Fig. 19 is a diagram that illustrates one aspect of attachment point architecture in accordance with the described embodiment. Fig. 20 is a diagram that illustrates one aspect of the Fig. 17 architecture. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT Overview The methods and systems described just below provide a mechanism by which functionality can be added dynamically to an application program or software platform. Functionalities or "extensions" as they will be referred to, can be advantageously added via a network such as the Internet. Extensions, that can implement new features or add to existing features, can be added using only a network address, such as a URL, as a basis for extension installation. That is, all of the files that comprise an extension can be maintained on the network and accessed via one or more network sites. Extensions can be described in a variety of ways. One way utilizes a hierarchical tag-based language which facilitates handling and use of the various extensions. In one particular implementation, a software platform is provided mat can incorporate various functionalities. The software platform and the inventive architecture described below enable third and fourth party developers to develop extensions for the platform that can be easily and seamlessly incorporated into the platform without having any knowledge of (or relationship with) a hosting service. A third party developer is a developer who develops an extension for the platform. A fourth party developer might be a developer who develops an extension to a third party developer's extension. Thus, the incorporation of third and fourth party extensions is essentially a transparent process, as far as developers are concerned. Consider for example, Fig. 1 which shows a user's computer 100 and several so-called extension sources 102,104, and 106. The extension sources can comprise any entity from which a software extension can be obtained via a network. In an exemplary implementation, the network can comprise the Internet, although other networks (e.g. LANs and WANs) can certainly be utilized. Extension sources can include, without limitation, business entities such as retail stores that might maintain a network site. In one implementation, a user can execute software on their computer that provides an application program or software platform. In this document, the terms "application program" and "software platform" will be used interchangeably. Each of the different extension sources 102-106 can provide software extensions that can plug into the software platform that is executing on the user's machine. These extensions are deliverable via a network such as the Internet, and assist in providing applications that can be executed on the user's machine. In the described embodiment, the extensions are logically described in XML which is in line with emerging industry standards. Additionally, the use of XML assists in the future discoverability of extensions by promoting XML DOM properties on the Internet. It will be appreciated, however, that any suitable format can be used for describing the extensions, e.g. a binary description could be used. Extensions can be delivered from any number of different extension sources. The inventive methods and systems provide a streamlined and organized way to handle the provided extensions. The use of XML advantageously enables efficient handling of extensions from multiple different extension sources, without unduly taxing the software components that utilize specific portions of an extension or extensions. In one particular implementation, the software platform on the user's machine provides various different integrated functionalities that enable a user to accomplish different document-centric tasks. An exemplary system is described in the U.S. Patent Application entitled "Single Window Navigation Methods and Systems", incorporated by reference above. Exemplary Computer Environment The embodiment described just below can be employed in connection with various computer systems. A computer system, for purposes of this document, can be considered as any computing device that includes some type of processor, i.e. a microprocessor, and some type of operating system. Thus, a computer system can be construed to include, without limitation, traditional desktop computers, more powerful servers, various hand-held devices such as cell phones, pocket-held computer devices and the like. Fig. 2 shows but one exemplary computer system that can be used to implement the embodiments described herein. Computer 130 includes one or more processors or processing units 132, a system memory 134, and a bus 136 that couples various system components including the system memory 134 to processors 132. The bus 136 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. The system memory 134 includes read only memory (ROM) 138 and random access memory (RAM) 140. A basic input/output system (BIOS) 142, containing the basic routines that help to transfer information between elements within computer 130, such as during start-up, is stored in ROM 138. Computer 130 further includes a hard disk drive 144 for reading from and writing to a hard disk (not shown), a magnetic disk drive 146 for reading from and writing to a removable magnetic disk 148, and an optical disk drive 150 for reading from or writing to a removable optical disk 152 such as a CD ROM or other optical media. The hard disk drive 144, magnetic disk drive 146, and optical disk drive 150 are connected to the bus 136 by an SCSI interface 154 or some other appropriate interface. The drives and their associated computer-readable media provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for computer 130. Although the exemplary environment described herein employs a hard disk, a removable magnetic disk 148 and a removable optical disk 152, it should be appreciated by those skilled in the art that other types of computer-readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, random access memories (RAMs), read only memories (ROMs), and the like, may also be used in the exemplary operating environment. A number of program modules may be stored on the hard disk 144, magnetic disk 148, optical disk 152, ROM 138, or RAM 140, including an operating system 158, one or more application programs 160, other program modules 162, and program data 164. A user may enter commands and information into computer 130 through input devices such as a keyboard 166 and a pointing device 168. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are connected to the processing unit 132 through an interface 170 that is coupled to the bus 136. A monitor 172 or other type of display device is also connected to the bus 136 via an interface, such as a video adapter 174. In addition to the monitor, personal computers typically include other peripheral output devices (not shown) such as speakers and printers. Computer 130 commonly operates in a networked environment using logical connections to one or more remote computers, such as a remote computer 176. The remote computer 176 may be another personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to computer 130, although only a memory storage device 178 has been illustrated in Fig. 2. The logical connections depicted in Fig. 2 include a local area network (LAN) 180 and a wide area network (WAN) 182. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet When used in a LAN networking environment, computer 130 is connected to the local network 180 through a network interface or adapter 184. When used in a WAN networking environment, computer 130 typically includes a modem 186 or other means for establishing communications over the wide area network 182, such as the Internet, The modem 186, which may be internal or external, is connected to the bus 136 via a serial port interface 156. In a networked environment, program modules depicted relative to the personal computer 130, or portions thereof, may be stored in the remote memory storage device. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used. Generally, the data processors of computer 130 are programmed by means of instructions stored at different times in the various computer-readable storage media of the computer. Programs and operating systems are typically distributed, for example, on floppy disks or CD-ROMs. From there, they are installed or loaded into the secondary memory of a computer. At execution, they are loaded at least partially into the computer's primary electronic memory. The invention described herein includes these and other various types of computer-readable storage media when such media contain instructions or programs for implementing the steps described below in conjunction with a microprocessor or other data processor. The invention also includes the computer itself when programmed according to the methods and techniques described below. For purposes of illustration, programs and other executable program components such as the operating system are illustrated herein as discrete blocks, although it is recognized that such programs and components reside at various times in different storage components of the computer, and are executed by the data processors) of the computer. Extensions An "extension", as used in this document, will be considered to include, without limitation, software functionality and content that can be added to an application program or software platform. These additions typically provide some type of functionality that the application program may not have had before the extension was incorporated, or alter the behavior of at least one existing feature. The extension is incorporated or integrated directly into the application program in a way that changes, to some degree, the manner in which the application program behaves or operates. Extensions provide dynamically added content and can provide applications (such as an email application), plug-ins to extend existing applications (like a fax plug-in to an email application), or simply web pages, to name just a few. In the described embodiment, extensions are described using XML, an industry-standard, text-based markup language. XML greatly facilitates the extensibility of software content Specifically, various extensions can be authored by third parties and described in XML in a manner mat enables the extensions to be readily integrated into application programs. It should be appreciated, however, the XML constitutes but one exemplary way of describing and using the extensions. Other ways can, of course, be used. Exemplary Extension Organization In the described embodiment, extensions are organized in three separate but related portions: an Extension Definition File (EDF), a Package Manifest (PKG), and the code, components, or "bits" that make up or define the extension. An EDF can be, but need not be associated with a URL (Universal Resource Locator) that provides a way for a Eent to access the EDF. By convention and choice, the PKG file is located at the same URL as the EDF. It will be appreciated that the described EDFs and PKG are each not required for the other to be used. It just so happens that, in the example mat is given is this document, the two are employed together. To that end, each of these features can be separately and independently employed. EDFs describe logical attachments to an application program or software platform, while PKGs specify the physical files and resources that are used in an extension. There can be a one to one correspondence between EDFs and PKGs. Fig. 3 shows an exemplary organization 300 that includes an EDF 302 and a corresponding package manifest (PKG) 304. In the illustrated example, the EDF 302 uses XML to describe the logical attachments or extensions to an application program. The corresponding PKG 304 specifies the physical files and resources that are associated with a particular extension. Exemplary file types are shown to the right of PKG 304 and include, without limitation, HTM, GIF, UDO, XML, DLL, and various other types of files. Extension Definition File (EDF) In me described example, an EDF is an XML file that logically describes an extension. For example, the EDF can describe HTML that makes up a user interface (UI), the objects that contain code for implementing various functions, and the like. The EDF can also contain all or part of the functionality mat comprises an extension. For instance, the HTML that describes a toolbar could be incorporated directly into an EDF file, and a toolbar attachment manager could read it from the EDF file, instead of from a URL. The information contained in the EDF is processed and (together with the information contained in the PKG), the appropriate files are automatically installed on a user's computer. This is done unobtrusively without manipulating the computer's persisted settings, as might be found in the user's system registry. An EDF, implemented in XML, contains various tags that are associated . with various extensions. The various tags can correspond to: • User interface elements • Behaviors/Components/Objects • Store Elements • User-defined objects • Or anything else that represents a point of extensibility in the application or platform EDFs advantageously have an "open schema" which means that third party developers can extend the extension mechanism and include their own extensions by creating their own tags. Additionally, extensions can themselves be extended by other developers. EDFs can also have one or more predefined tags. Exemplary predefined XML tags for user interface elements can include tags for feature types such as: tool bars, accelerators, menu items, and themes. These feature types are utilized in the single navigable window application incorporated by reference above and defined in the table immediately below: Feature Type Definition Tool Bars Horizontal command containers above the document area. Accelerators Keyboard shortcuts for commands Menu Items Pop-up or drop-down menu choices that third parties can add to well-known, named menu attachments in the platform Themes A data-driven way to provide overrides for well-known resources of the platform, such as default buttons or default style sheet Table 1 Exemplary predefined XML tags for behaviors/cornponents/objects include tags for Services. These feature types are utilized in the single navigable window application incorporated by reference above and defined in the table immediately below: Feature Type Definition Services Services are objects that extend existing objects (such as the application, window, or document) in the application or platform's Object Model. For example, editing functions use Object Model Attachments attached to the window or document that maintain document context and editing state per-window. These can also include Object Model Attachments attached to the application (such as a spellchecker dictionary object) Table 2 Exemplary predefined XML tags for store elements include tags for content classes and offline data sources. These feature types are utilized in the single navigable window application incorporated by reference above and defined in the table immediately below: Feature Type Definition Content Classes Allow extension writers to define new types of XML documents with new schemas. Offline Data Sources Allow for extension writers to define store replication instructions in an EDR Table 3 ID EDF Schema In the described embodiment, the EDFs have a particular XML schema that is utilized. The schema comprises collections of XML tags that are arranged in a hierarchical organization to facilitate information dissemination to software components that need certain extensions. In the described embodiment, the outer (encompassing tag) for EDFs is an "extension" tag. Fig. 4 shows an exemplary extension tag. "extension" tags can include one or more of the following attributes, all of which are optional: Attribute Definition Urn ID for the extension. It allows extension writers to specify relative locations for content in EDFs without using relative paths or fixed URLs. It also allows hosting administrators to move around extensions on servers without breaking any links. Name Name that can be used in a status bar or message display Version Vendor-determined version number for the extension. lastUpdate Date/time mat the EDF was last modified. description Brief description of the extension. Table 4 15 Within the "extension" outer tag are one or more child tags, also referred to as "top level tags". These top level tags are each associated with a feature type that can be added by a particular extension. Exemplary feature types are discussed in connection with Tables 1-3 above. Underneath each top level tag there can be one or more child tags that are individually associated with a particular feature of the feature type that is to be added by a particular extension. Fig. 5 shows an exemplary XML schema organization in accordance with this embodiment. For each top level tag in an EDF, there is an associated attachment manager which is a software component that receives data associated with the tag so that the data can be used to incorporate the extension into the platform or application program. Different attachment managers may interpret the data from the tag in different ways to provide different types of extensibility, so different top level tags will contain different types of data in different structures. This will become more evident in the "Architecture" section below. Note that the "edf:" XML namespace qualifier enables support of an open schema where extensions can provide their own tags and corresponding attachment managers. Tags within the edf namespace are used by built-in attachment managers in the application or software platform. Tags in other namespaces are used by third-parties to provide additional points of extensibility. Package Manifest (PKG file) The package manifests (PKGs) assist in organizing the downloading of software in the form of multiple files over a network such as the Internet The PKGs are advantageously employed, in the example given in this document, with EDFs. As pointed out above, however, the techniques discussed in connection with the PKGs can be deployed independently of EDFs and in any suitable scenario where it is desirable to deliver software over a network such as the Internet While the EDFs describe the logical attachment of extensions into an application program or platform, the package manifest's role is to assist in one or more of: organized delivery, validation and/or, updating of files associated with the various extensions that can be provided. In designing a delivery mechanism for Web-assisted delivery of software content or files, several considerations are of interest Whenever possible, it is desirable to reduce the size of required downloads during update and installation operations. To address this consideration, software content is broken into multiple packages. Each package contains a group of one or more files that implement a common or well-defined functionality. By breaking the content into individual packages, the size of the required download during installation and update can be minimized. Each package is then described by a package manifest (PKG) that includes file information such as file locations and hash values mat can be used for validation or security and versioning. It is also desirable to give the end user a Web-like experience. To do this, extensions are loaded in a manner that feels to a user more like they are loading a web page, rather than traditional software packages where the user has to wait until the entire package is loaded before they can interact with it In the described embodiment, users are given a web-like experience by streaming the extension files down to the client so that a user can begin to interact with an application program much sooner than if they had to wait for the entire software application program to load. For example, if there are user interface (UI) image files streaming down, the user can see the UI as the files stream in. Consider, for example, the single application program having the multiple different functionalities that is described in the patent application incorporated by reference above. A user might browse to an email functionality and download the files that are necessary to interact with the email functionality. Files that are associated with another different functionality would then be downloaded after the files associated with the email functionality. In this way, the user can begin to operate within a particular functionality without having to wait for all of the files associated with all of the other functionalities. Another consideration of interest pertains to the efficiency with which the extension files or "bits" are delivered to the client To address this consideration, the described embodiment utilizes a couple of different download approaches: a throttled download and a background download. Throttled downloading conducts download operations while taking into account the available bandwidth and type of media over which the files are being transferred. Any suitable throttled download process can be employed and will be understood by those of skill in the art. Background download is conducted while the user is working within the application program and is implemented by allocating a background thread so that the user can continue their work. One optimization that is utilized is that packages are prioritized and delivered in accordance with what a user might be working on. Another consideration is associated with optimizing the user's computing experience. Here, the user's experience is optimized by making available the most common scenarios for the user. This is effectively directed to giving me user the functionality that they want first, and then, through the background download process, providing the code that implements functionalities that the user might use in the future. To determine which functionalities a user desires to have first, an automated scenario-based packaging process is provided mat runs against file usage logs from scripted scenarios. All of these considerations and the inventive solutions directed to addressing the considerations are discussed in detail in the sections that follow below. Package Manifest Definition In the described embodiment, a package manifest (PKG file) comprises a list of files mat are utilized in a package. The list is advantageously compressed somewhat and digitally signed. Each package manifest can contain a list of one or more files each of which can include an associated hash, as well as download directives that control caching of the files. Once an extension is authored, a software tool can be used to generate the package manifest In addition, the package manifest can specify several other pieces of information: • FILE GROUP All files in an extension can be labeled according to a number of predefined file groups. The file group of a particular file determines when the particular file gets downloaded, where it is stored on the client, and how it gets packaged. In die described embodiment, four predefined file groups are provided and are listed and described in the table immediately below: they are requested for the first time. package cache down individually. \ space on the client, advanced features can be put in this category. Online only Downloaded on demand. Content is only available when the user is online. Winlnet Cache Files are sent down individually Content that is not to be provided offline. Examples include help pages and other content that can consume a large amount of disk space. * CAB stands for the CABinet technology that Internet Explorer uses to package bits tor download. CAB files average from 2 to 3:1 compression, and are optimized for quick expansion. CAB files have the added security benefit that they arc easily signed. • FILE DOWNLOAD PRIORITY Files in each, group are listed according to the order in which they should be downloaded. This download order is implicit in the ordering of the files in the ackage manifest, an example of which is shown in Fig. 6. • HASH VALUE FOR SECURITY/VERSIONING Individual files in the package manifest can have an associated hash value. Each hash value is generated by running the file through an encryption algorithm. An exemplary encryption algorithm is Microsoft's CryptoAPI. In the illustrated example, each file can be listed with a base 64-encoded hash value, so that the file can be validated once the content arrives at the client. Specifically the package manifest is sent to the client in a secure manner (i.e. it is digitally signed). The package manifest contains the hash values for individual files. When the individual files are received by the client, each of the files can be run through the same Crypto API that was used to provide the hash values in the package manifest. If the hash values for a particular file compare favorably, then the file has not been altered and is secure. When a file is updated, hash values can serve a useful purpose in identifying files that have not been changed between different versions of an,extension. Consider Fig. 7, for example. There, an old directory 700 in a client package cache contains package A which include two files—file 1 with hash = x, and file 2 with hash = y. Assume that this package is associated with an older version of an extension. When an updated version is produced, its package manifest is delivered to the client. The updated extension version is represented on a source directory of a code or web server 704. The package manifest includes the hash values for all of the files in the new extension version. A new client destination directory 702 is defined for all of the files of the new extension. If any of the hash values for files in the new extension axe the same as the hash values of the files in the old directory 700, then those files can be copied directly from the old directory 700 to the new destination directory 702. In this example, file 1's hash value is the same as the hash value for file 1 on the source directory 704, so it can be copied into the new destination directory 702. File 2's hash value, however is different from the hash value for file 2 on the source directory, so it is not copied from the old directory 700. Rather, file 2 is downloaded from the code server. A new file 3 has been added and is also downloaded from the code server. Hence, in this example, a new version of an extension resulted in a download of less than all of the files in the extension version. This is because hash values for each of the files in the old extension version were able to be compared with hash values of the files in the new extension version. Those hash values that are the same indicate files that have not changed as between versions. Using hash values for versioning has two important advantages over traditional versioning schemes. First, the update process is automatic. That is, with an explicit version number, it is possible to forget to update the version number when shipping a new release of a file. Using hash values avoids this problem. Second, versioning does not rely on file types. Specifically, traditional versioning schemes commonly embed version information within files; however, not all files (e.g. GIF files) support embedded version information. In the present example, using hash values for versioning does not depend on whether a particular file type supports or does not support embedded version information. In addition, the version information can be stored separately from the file itself. Thus, access to actual file to determine whether it is current is not needed. • TOTAL STORAGE SIZE OF PACKAGE The total storage size of a package is useful at download time to verify that the user has sufficient disk space. • ClassID's FOR THE DLLs Listing ClassIDs for each DLL is necessary to enable script writers to create classes by scripting against the OM. Additionally,' this enables a determination of which package contains the code for a particular class. • DLL LOAD DEPENDENCIES The reason for the dependencies section is to allow for legacy code that relies on being loaded by virtue of being in the search path of some other dll. In this case we have to make sure that the dependency dll is in the package cache directory before the dependant dll is loaded. Fig. 6 shows an exemplary package manifest 600 that is defined in a hierarchical tag-based language. Advantageously, the tag-based language comprises XML which is desirably extensible and flexible. In this example, a number of tags are provided in a hierarchical arrangement. The "package" tag contains infonnation about the size of the package. The "files" tag is a child of the "package" tag and contains information about the file groups that are contained in that particular package. The "file" tag is a child of the "group" tag and contains information about specific files that comprise the extension, i.e. file name and hash value. A "dependency" tag is provided as a child of the "file" tag and lists any dependencies as discussed above. A "COMClass" tag is also provided as a child of the "file" tag and contains IDs as mentioned above. The ordering of the file groups in this schema implicitly defines the download order of the files. Package Delivery To optimize package delivery, two different delivery schemes are utilized. First, a throttled download approach is utilized using known throttling download techniques. Here, considerations such as available bandwidth and media over which the extensions are being provided are considered. Second, a background download approach is utilized. Background downloads enable a user to continue to work within an application program while content is downloaded. Foreground downloads are used when the user has explicitly requested a file/extension by clicking, for example, on an extension link, or requested an action, for example, by clicking on the "Compose" mail button, mat requires download of files which are not available locally. Along with background downloads, a queue management feature is provided. Specifically, when an extension must be installed or updated, a package manager, which is essentially a software component that manages packages, is provided with the following information: • URL for the package manifest information on a code server • URN for package destination directory in the package cache at the client • (Optional) URN for the old package directory (if one exists) in the package cache From this information, the package manager creates a package object and adds the package object to a download queue. The download queue is designed for easy rearrangement of a package download order. Consider, for example, Fig. 8 which shows a portion of a download queue 800 that contains two package objects—package object 802 (corresponding to package A) and package object 804 (corresponding to package B). The package objects maintain a list of which files of a corresponding package have been downloaded or installed. In the present example, files 1 and 2 from package A have been installed while file 3 has not been installed; and files 1, 2, and 3 have not been installed from package B, The download queue can be rearranged based on what the user is doing. That is, based on the actions that a user takes, the priority of files that are to be downloaded can be changed. In this example, the package manager is designed to process the first uninstalled file in the package at the head of the download queue. If, however, the user starts to use a file in an extension that is different from the extension whose files are at the head of the download queue, the corresponding package for the file that the user has started to use can be moved to the head of the download queue. Because a file's package is specified by its URN, the file's package can be quickly identified and located in the download queue. For example, and considering Fig. 8, if one of the files in package B is requested before the package manager has started to install package A's third file, then package B will be moved to the head of the download queue. Fig. 9 is a flow diagram mat describes steps in a download queue management method in accordance with the described example. The method can be implemented in any suitable hardware, software, firmware or combination thereof. In the present example, the method is implemented in software. Step 900 receives one or more requests for an extension. The requests can be generated in any suitable way. Step 902 creates a package object that corresponds to each extension package that is to be downloaded. Step 904 arranges the package objects in a download queue. Step 906 then downloads files corresponding to the package objects in the download queue. This step can be implemented by, for example, starting at the head of the download queue and downloading files until all of the files for a package object have been downloaded, and then moving to the next package object. Step 908 ascertains whether a user action requires a file that is not described in the current package object. If the user's action does not require a file not described by the current package object, then the method branches back to step 906 and continues to download files associated with the current package object. If, on the other hand, the user's action requires a files that is not described in the current package object, then step 910 moves the package object associated with the required file to the head of the download queue and begins to download files associated with mis newly-repositioned package object. This step can be implemented by ascertaining which package object is associated with the required file by ascertaining the URN associated with the file. This URN specifies the file's package so that its package object can be quickly located and moved to the front of the download queue. Package Creation One of the innovative features of the described embodiment is its extensibility. That is, a software platform is provided in the form of an application program that can be extended by various'third-party user-defined extensions. These extensions are delivered via the Web and are integrated directly into the software platform. In order to provide an organized delivery process, packages should be created in a uniform manner so that they can be predictably handled and integrated into the software platform. In accordance with the described embodiment, each package should correspond to an end-user feature. For example, in the patent application incorporated by reference above, separate packages are provided for each of the email, contacts, document authoring, and planner functionalities. If packages that do not depend on one another share a dependency, then this shared dependency should become its own package. For example, there is no reason why the email and document authoring functionalities should depend on one another, yet both of them require the ability to publish content By separating the publishing functionality into its own package, a certain amount of download order flexibility is preserved. Depending on what the user starts to work on, the files corresponding to the email functionality or the document authoring can be downloaded first. Fig. 10 is a flow diagram that describes steps in a package creation method in accordance with the described example. The method can be implemented in any suitable hardware, software, firmware or combination thereof. Portions of the method might, however, be implemented manually. Step 1000 identifies end user features that are to be provided as extensions. Step 1002 identifies any shared dependencies among the end user features. Step 1004 creates individual packages for the end user features. Step 1006 creates individual packages for any shared dependencies among the end user features. Automated Package Manifest Creation Tool Advantageously, and in accordance with one implementation, an automated package manifest tool is provided and takes various input parameters and automatically creates a package manifest. The tool can be available to third parties to assist them in creating a package manifest. Fig. 11 shows an exemplary package manifest creation tool 1100 that is desirably implemented in software. In this specific example, the tool can take the following input parameters (some of which are optional): • Extension directory • File group information and DLL load dependencies (Optional) • File usage statistics from scenario runs (Optional) The extension directory input parameter specifies the directory containing all of the files mat will he described by the package manifest. If this is the only parameter, then tool 1100 will generate a manifest in which the EDF and DLLs in the directory are listed in the "Required" set, and all other content is "Offline". The file group information and load dependencies parameter is optional. If an extension author has an idea of the categories in which his or her files should be placed, the categories should be specified here. For example, the author of the template manifest shown below knows that he wants his error handling GIF to be included in the package's required set His choices here will always be respected in the final manifest. Additionally, if the extension author knows of any DLL load dependencies, these should be specified here as well. The file usage statistics from scenario runs parameter is an optional parameter. This parameter enables the file download priority to be determined based on scenario runs. A scenario is a script of tasks that the average user typically follows when using a product during a particular portion of product use. For example, one scenario might pertain to the tasks involved, in sending an email message (i.e. click "new mail" button, type in "TO" well, type is "Subject" well, etc.). In the described embodiment, file usage statistics from scenario runs are collected from running IIS logs on various scenarios. The different scenarios are directed to ensuring, with some degree of probabilistic support, that the file download order reflects, in some way, the files that will likely be used by the user first. It will be appreciated that the file usage statistics can be provided dynamically by building a knowledge base that describes the actual tasks that people typically accomplish. The information that is maintained in the knowledge base can then be used to generate and adapt download scenarios that actually conform to patterns that are established across a user base. If extension writers want to pass the package manifest creation tool 1100 this information, they need to specify the log directory, as well as the start and end dates of the section of the log that the tool should analyze. For third parties, the download priority order within a group will be the order in which the group's files were requested in the logs across all scenarios. In one implementation, the approach is somewhat more sophisticated. Additional information (in addition to the scripted steps) is stored in the US logs and includes scenario priority and checkpoints. The scenario priority is a priority that is assigned for each scenario. So, for example, if one scenario is ten times more important than another scenario, this information can be maintained. The priority (e.g. a rating from between 1 to 100, with 100 being the highest priority), should be equal to a best guess as to the percentage of the time that users will step through the scenario, assuming they use the extension at all. Checkpoints provide a way to separate one scenario from another. For example, checkpoints designated as "Offline" and "Shutdown" can be automatically added at the beginning and end of the scenarios, respectively, so there can be a differentiation between scenario runs in the log. Additionally, script authors can optionally use checkpoints mid-scenario to indicate a change in group priority, e.g. part of a scenario script could be labeled as an "On demand" feature and another part could be labeled as "Offline". Fig. 12 is a flow diagram that describes steps in a package manifest creation method in accordance with the described example. The method can be implemented in any suitable hardware, software, firmware or combination thereof. In the described example, various steps of the method are implemented by a manifest creation tool that is implemented in software. Step 1200 provides a package manifest creation tool. This tool can be a software tool that resides on an extension author's machine. Step 1202 receives information pertaining to an extension directory as a first input parameter. Step determines whether there is any file group information or load dependency information provided by the extension author. If there is, step 1206" receives the information as an input parameter. Step 1208 determines whether there is any file usage statistic information. Such information can be provided, in one embodiment, through the use of scenario runs as described above. If such information is provided, then step 1210 receives the information as an input parameter. Step 1212 then uses all of the information provided as input parameters to generate a manifest automatically. Exemplary File Ordering Heuristics Based on File Usage Statistics Fig. 13 is a flow diagram that describes but one exemplary file ordering or sorting heuristic in accordance with the described embodiment. It is to be understood that this specific example constitutes but one way of ordering files for download. Accordingly, other heuristics can be used without departing from the spirit and scope of the claimed subject matter. Step 1300 sorts files by file group. Recall that in the illustrated example above, files can be grouped in one of four possible groups: Required, Offline, On Demand and Online Only. A file's group is determined first by me manifest, and, if it does not provide any group information, then by the highest priority group that it uses, according to checkpoint information in the log. Files in the "Required" set should not be considered because their order is already known. If no group mformation is included about a file, then an assumption is made that the EDF and all DLLs are "Required" files and all other files in the directory are "Offline". Consider, for example, the following initial file usage information for three different scenarios: Scenario 1 file usage: l)FileA.gif 2)FileB.xml,, 3)FileE.dll Scenario 2 file usage: 1) FileCxml, 2) FileA.gif Scenario 3 file usage: l)FileD.js, 2)FIleA.gif Scenario 1 = priority 80 Scenario 2 = priority 80 Scenario 3 = priority 40 In this example, there are three scenarios that have files associated with them. Each of the scenarios has a priority with which it is associated. The files are first sorted by group (step 1300). Recall that in this ordering heuristic,' DLLs are "Required" and all other files are considered "Offline". This provides the followmg sorted files: Required files FileE Offline files FileA, FileB, FileC, File D Step 1302 sorts files based on scenario priorities (from highest to lowest). Higher priority files are ordered so that they are downloaded first. This step provides the following sorted files: Required files FileE Offline files Priority 80 group: files used by Scenarios 1 & 2 = File A, File B, and FileC Priority 40 group: files used by Scenario 3 (that are not already listed) = File D. Step 1304 men sorts the files by file usage order within a scenario run. For each priority grouping with more than one file, the files are sorted according to the average order in which they were downloaded within scenarios of their labeled priority. Scenarios with a smaller average usage order will be downloaded earlier. Ties are broken based on the order in which the scenarios appear in the input file. As an example, consider the following: File A: average order = (Scenario 1 order + Scenario 2 order)/2 = (l+2)/2 = 1.5. File B: average order = (Scenario 1 order)/1 = (2)/l = 2. File C: average order = (Scenario 2 order)/l = (1)/1 = 1. Here, file A got used first by scenario 1 and second by scenario 2 for an average of 1.5, and so one. File C has the smallest order number so, of me Offline 5 files, it is sent first. The final file order is shown below: Required files FileE Offline files FileC,FileA,FileB,FileD Code, Components and "bits" The following files and resources can be, but need not be included with an 5 extension. This list is not exclusive, as other resources can certainly be incorporated into an extension. • Customized UI and keyboard shortcuts • Components and Behaviors • XML browsing and editing components (including XSL and business logic objects) • Static pages or other resources • Third-party defined custom content Users install extensions by navigating to a network site for the extension. In an Internet implementation, the user navigates to an appropriate URL for the extension. Hosting administrators can also "push" extensions so that users can automatically receive them by adding an entry into the appropriate users' "Preference" settings. Platform Set Up and Extension Installation Fig. 14 is a flow diagram that describes exemplary steps in a set up and extension installation process in accordance with the described embodiment. This example describes an Internet-based example. In the illustrated example, various extensions are maintained at or accessible through various Internet sites. The extensions are deliverable via the Internet to a client. It will be appreciated that the illustrated division of computers may not necessarily exist at all. For example, all of the functionality embodied by the computers may reside on one machine, or the extension may be local, or the platform and the extensions may be on the same machine, etc. The flow diagram, in this example, is illustrated in connection with three separate "zones", one of which represents a client, one of which represents a "platform" Internet server, and one of which represents a third party Internet server. The acts that are described in connection with the different zones are performed, in this example, by the entities assigned to the zone. In some configurations, one or more of these zones may overlap. For instance, the platform server may be the same device as the extension server. . Step 1400 navigates a user to a particular Internet site that is associated with the software platform that is to be utilized as the foundation for extension installation described below. In step 1402, the user cricks an "install" button that sends a message to the software platform server that indicates that a user wishes to install the software platform. This step can be an optional step. Steps 1404 and 1405 then download the software associated with the software platform to the client. In the illustrated example, step 1404 downloads the package file for the single navigable window application and based on mat file's contents step 1405 downloads other components and files to the user's computer. Step 1406 installs the software code on the client machine and can create local directories for the application cache, a local store and preferences. It will be appreciated, however, that local directories or preferences are not necessarily needed. Step 1408 launches the software platform. The steps described immediately above constitute steps associated with an initial set up in which the software code for the single navigable window application is delivered to and installed on a client machine. The steps described immediately below are associated with extension installation. Step 1410 uses a link that is associated with an extension to access the extension. This step can be implemented by a user navigating their browser to a particular Internet site through which one or more extensions can be accessed. Alternately, a reference to the link can be placed in the user's preferences or the preferences of a computing group with which the user is associated (e.g. the system administrator can place a reference in a group's preferences). The link can advantageously be associated with a third party Internet server or Internet site. Step 1412 downloads extension files according to the PKG associated with an EDR The files are delivered to the client and step 1414 places the extension files in a local store as specified by the PKG specification. At mis point, an extension is installed and the user can utilize the functionality provided by the extension. Step 1416 determines whether extension updates are available. This can be done by periodically polling an extension catalog (discussed in an "Extension Catalog" section below) to ascertain whether mere are any updates to various extensions. Alternately, notifications might be automatically sent to the client so that the client is aware of updates or any other method might be used to determine if updates are available. If mere are updates available, step 1418 branches to step 1412 which downloads the extension files associated with the update and installs them on the client Developing Extensions Developing extensions for the software platform is a fairly straight-forward process. A developer develops the extension content using a tool such as Notepad or other tools such as Visual Studio. The extension is then described in an EDF and PKG and the PKG is digitally-signed and then optionally compressed. The extension can then be hosted on a particular network server. Fig. 15 is a flow diagram that describes steps in an extension development method in accordance with the described embodiment. One or more of these steps can be performed by a software developer or organization that creates a particular extension. Some of the steps are implemented in software. Step 1500 develops an extension. Any suitable tools can be used to develop the extension. Step 1502 then creates an extension definition file (EDF) for the extension. The EDF, in this example, is defined using XML as discussed above. Other formats can, of course, be used to describe the EDF. Step 1504 creates a package manifest (PKG) for me extension. The PKG, in this example, is defined using XML as discussed above. Step 1506 then hosts the EDF and PKG on a network server such as an Internet server. Additionally, the associated extension files that are described in the PKG can also be hosted by the network or Internet server (step 1508). Having accomplished the above, users can now navigate to an EDF directly (using, for example, the associated URL or some other network address), which then installs the extension by caching any required files locally and placing a reference to the extension in the user's preferences. Specifically step 1510 delivers the EDF and PKG files to a client. This step can be implemented by a user navigating to a particular Internet site where the appropriate files are hosted and then downloading the files. Step 1512 delivers the extension files that are associated with the EDF and PKG files to the client, whereupon they can be installed and used. Extension Catalog One optimization, discussed briefly in connection with Fig, 14, is an extension or EDF catalog which provides an additional level of indirection to the EDF. An EDF catalog allows organizations to group extensions and provides a single place to detennine when an extension changes. The desired extension can be automatically selected from the catalog by the software platform based upon the user's settings. The catalog can be queried to determine which extension is most appropriate for the user. In the described embodiment, a catalog is an XML file that contains mappings from extension URNs to one or more package URNs based upon language, version or other attributes. Catalogs can, however, be defined using any suitable format. Catalogs can provide: • The ability for a hosting organization to update version information for one or more hosted extensions in a single place • Optional automatic indirection to correct version based upon user's settings. For instance, a catalog may list several versions of an extension for different languages. The catalog file can be processed to find the version of the extension that matches the user's language settings. • Optional automatic upgrade to new versions of extensions as they become available Like EDFs, catalogs can be compressed and digitally signed to prevent tampering. By subscribing to a catalog in order to detect changes for one or more hosted extensions, the number of server pings required from the client (or notifications to the client) in order to discover extension updates can be reduced. Fig. 16 shows an exemplary XML catalog structure. Entries in the catalog can be structured as follows: Attribute Type Required Description extensionURN uri Y Identifier for an extension. Here may be more man one entry, for a given extension urn in a single catalog representing different versions, languages, etc. Name String N Friendly name for an extension. packageURN uri Y Required urn for the package. Package urn corresponds to a discrete set of bits. It is different from the extension urn: For each user, the extension urn (name) corresponds to a specific set of files based upon language preferences and version. This means that, for shared machines, different users may have different extensionURN to packageURN maps based upon their preferences. packageURL uri Y url of the digitally signed compressed file containing the PKG file is required. language String N Language is an optional language specifier. Version String N Version is an optional version specifier defaultLanguage String N DefaultLanguage is an optional attribute specifying the default language package. For a given version of an extension, there should be only one entry with DefaultLansuage attribute. defaultVersion string N Default Version is an optional | attribute specifying default version for an extension. For a given extension urn and language attribute there should be only one entry with DefaultVersion attribute. In this particular example: • The default language of the netdocs-plarmer is the English version. • The default English version is 1.1. The default French version is 1.0. If there is no version available in the user's specified language on the platform, they will get the English version 1.1 by default. • The English version of netdocs-planner has been upgraded from VI to Vl.l. • There is also a French version. The extension URN is the same as the English version. There is no 1.1 release for French yet, so 1.0 is the current version for French speaking users. • A query against the catalog returns only the rows where language matches the user's language preferences. The query would also return all rows where language is the user's language or default = 'yes'.and throw out duplicates for the same name. Architecture In the described embodiment, one of the aspects that provide desirable utility is the extensibility of the software platform. That is, third and fourth party developers are free to develop their own extensions which can then be used within the framework of the software platform. The extensions are integrated directly into the software so that the platform's functionahty is modified by the extensions. Recall that in order to provide an extension, the developer simply authors the extension, describes their extension in an EDF and PKG, and then hosts the EDF, PKG, and associated files on a network server. The EDF, as pointed out above, can be defined in an XML schema that includes a root node (i.e. the "extension" tag) and one or more child nodes. In this particular example, the child nodes generally correspond to the individual extension feature types that are desired for incorporation into the software platform. For example, recall that Tables 1-3 above describe various exemplary predefined feature types that can be added through an extension using the predefined XML schema. Consider now a developer who wants to add two menus and a toolbar to the software platform. The menus and toolbar might be associated with a retail store that maintains a Web site for its customers. The retail store might want a customer who visits its Web site to be presented with a UI that is unique to the retail store and provides services that are specifically tailored to the store. To do this, the developer develops two different menus, one of which might be associated with displaying the most recent specials, and other of which might be associated with providing a search mechanism through which the user can search for specific products. The toolbar might contain specific buttons that are unique to the retail store. A simplified EDF called "retail.edf " for the retail store's extension is shown directly below: Here, the outer "extension" tag designates this XML file as an extension. The inner "menus" and "toolbars" tags are top level tags that designate that the information between ibese tags pertains respectively to meaus and toolbars that correspond to the extensions that the developer has added. The boldface ttmenu" and "toolbar" tags describe data pertaining to the actual extension and contain a URL that is associated with each extension as described above. The EDF above logically describes the extensions that are being provided as including two menus and one tool bar. Consider also that the above EDF can constitute but one of many EDFs that are loaded into the system. Each EDF can contain one or more top level tags, each of which is associated with one or more specific extensions that are to be added to the software platform, Fig. 17 is a block diagram of an exemplary software architecture that is configured to process multiple different EDFs so that the software components that are responsible for incorporating each particular extension into the software platform receive the appropriate information that is specific to their extension. This example is specific to the XML implementation that is discussed throughout this document It is to be understood that other architectures, similar in functionality to the one discussed below, can be used in other implementations without departing from the spirit and scope of the claimed subject matter. Utility objects, herein referred to as attachment points, are used to process the information from the multiple EDFs. An attachment point is simply a collection of objects that fire events to registered listeners as objects are added to or removed from the collection. Many types of attachment points can be created, but all take data from a source (often another attachment point), process it (either dynamically or statically), and expose the results of their processing. Some of the simplest attachment points include: • An XML attachment point, which loads an XML file and exposes me top-level nodes of the XML as objects in its collection. • A filter attachment point, that connects to another attachment point and exposes only those objects from it that meet some criteria. • A merge attachment point, that connects to one or more other attachment points and exposes all of their objects as one, merged collection of objects. In the illustrated example, the architecture includes a collection of one or attachment point manager 1702, and multiple attachment managers 1704. The EDFHub 1700 receives all of the EDFs and merges them together and exposes them as a single list. Other individual attachment points provide mechanisms that manipolate (mchiding filter, merge and expand) the single list that is exposed by me EDFHub 1700. Whenever a new extension or EDF is added to or removed from the EDFHub, the various attachment points will see to it that the appropriate attachment managers) is notified- This is done by firing events to the appropriate attachment managers. The attachment point manager 1702 creates, destroys and manages the various attachment points in the system and allows easy reuse of identical attachment points. For each top level tag (i.e. "menus" and "toolbars" tags), there is a corresponding attachment manager 1704 that uses data provided by the attachment points to incorporate a particular type of feature witha the software platform. Each attachment manager requests a set of attachment points from the attachment point manager 1702. These manipulate the data exposed by the EDFHub 1700. In the illustrated example, the attachment points can be requested as a predicate chain that the attachment point manager uses to create and build a set of attachment points diat operate on the data exposed by me EDFHub 1700. Fig. 18 is a flow diagram that describes steps in a method in accordance with the described embodiment The method is implemented in software and, in this example, by the software components of Fig. 17. Step 1800 receives multiple EDFs. These files can be received in any suitable way. For example, a user can specify in their preferences particular extensions that they desire to be loaded when they are online. Alternately, a user might navigate using a link to a particular Internet site mat recognizes mat the user is executing a software platform that is configured to dynamically add the extensions. The EDFs, in this example, are funneled into the EDFHub 1700 which uses attachment points to combine the EDFs (step 1802). In this example, the EDFs are defined as XML files and the nodes are combined into one single XML list Step 1804 exposes the combined EDFs. In this particular example, the EDFs are combined into a single XML list that is exposed to other various attachment points which then further manipulate that data (step 1806). One goal of the attachment points is to avoid having the attachment managers 1704 re-query the whole system every time an extension gets added or removed from the system. Thus, if an extension gets added or removed, the attachment points ensure that only the appropriate attachment manager 1704 is notified of the specific additions or deletions of the extension. For example, if an EDF indicates the addition of a menu, then only the attachment manager associated with menus is notified. Accordingly, step 1808 notifies the appropriate attachment manager of any new data that matches the attachment managers requirements. Attachment Points and the Attachment Point Manager Attachment points are objects that expose collections of ordered objects and fire notifications when new objects are inserted or deleted. In the exemplary system, the objects are XML nodes, but they could be any type of object. Although there are many types of attachment points, they all follow a similar process: 1) Initially attach to one or more data sources. These could be files or, commonly, other attachment points. 2) Process the data based on some logic. Usually the logic is quite simple and could involve something like filtering the objects based on some criteria. 3) Expose the results of the processing step 2 in a new collection of objects. 4) Fire events to indicate how the exposed collection of objects changed (On Inserted(index, count) or On Removed(mdex, count). 5) Optionally, continue to listen for changes in the data sources and repeat step 2-4 when changes occur. Alone, each attachment point is quite simple, but when different types of attachment points are combined to form "chains", where one attachment point processes data from a second attachment point, the processing can be quite powerful. This is especially true if the attachment points only process the changed data in step 2, since they only do a small amount of simple work at any one time. In the exemplary system, this incremental processing means that the whole system does not have to be re-queried when a new extension is installed or when an existing extension is removed. Additionally, each attachment manager in the exemplary system uses a specific chain of attachment points and so is only informed of changes that impact its area of extensibility. The attachment point manager performs two important functions when building chains of attachment points. First, it allows the chains to be described as predicate strings. The attachment point manager interprets these strings and builds the required chain of attachment points. Second, it allows the reuse of identical attachment points, which makes the system more efficient As the attachment point manager creates each chain of attachment points, it tracks which predicate string corresponds to which attachment point. If mat predicate string is later requested again, it simply reuses the existing attachment point without creating a new one. As an example, consider that the attachment manager associated with menus has requested the following predicate chain of attachment points that utilizes the retailedf file above: (Note: this example does not assume the presence of an EDFHub attachment point). Explode(Filter("menus", Explode (URL ("retailedf')))) This string represents all of the menus in the retail.edf file. The XML file located at retail.edf is loaded by the URL attachment point which exposes the root node of the XML file as the only object in its collection. The inner Explode attachment point uses the URL attachment point as its data source and exposes all of the children of the objects in that source collection. In this case, me children of the root node are the top level XML tags "menu" and "toolbars". The Filter attachment point uses the Explode attachment point as its data source and filters the exposed objects looking only for the nodes that are "menus". The outer Explode attachment point uses the Filter attachment point as its data source and exposes all of the children of me filtered menu nodes to provide a list containing the two menus that are added by the extension. Since this particular XML file contained menus that were identified by the attachment points associated with menu attachment manager, that attachment manager is then notified that two menus have been added by an extension. This process is diagrammatically illustrated in Fig. 19 which shows attachment points 1900, 1902, 1904, and 1906. Each attachment point exposes a list of XML nodes. URL attachment point 1900 takes an input (a URL to an XML file—e.g. retail.edf) and exposes a list of XML nodes. This list contains only the root node " point 1902 are the " |
|---|
in-pct-2002-01793-mum-claim(granted)-(13-12-2002).pdf
in-pct-2002-01793-mum-claims(amended)-(28-2-2006).pdf
in-pct-2002-01793-mum-claims(complete)-(13-12-2002).pdf
in-pct-2002-01793-mum-claims(granted)-(13-12-2002).doc
in-pct-2002-01793-mum-claims(granted)-(5-3-2007).pdf
in-pct-2002-01793-mum-correspondence(25-3-2010).pdf
in-pct-2002-01793-mum-correspondence(28-2-2006).pdf
in-pct-2002-01793-mum-correspondence(ipo)-(23-4-2007).pdf
in-pct-2002-01793-mum-correspondence(ipo)-(5-3-2007).pdf
in-pct-2002-01793-mum-description(complete)-(13-12-2002).pdf
in-pct-2002-01793-mum-description(granted)-(5-3-2007).pdf
in-pct-2002-01793-mum-drawing(13-12-2002).pdf
in-pct-2002-01793-mum-drawing(complete)-(13-12-2002).pdf
in-pct-2002-01793-mum-drawing(granted)-(5-3-2007).pdf
in-pct-2002-01793-mum-form 18(25-4-2005).pdf
in-pct-2002-01793-mum-form 1a(13-12-2002).pdf
in-pct-2002-01793-mum-form 2(complete)-(13-12-2002).pdf
in-pct-2002-01793-mum-form 2(granted)-(13-12-2002).doc
in-pct-2002-01793-mum-form 2(granted)-(13-12-2002).pdf
in-pct-2002-01793-mum-form 2(granted)-(5-3-2007).pdf
in-pct-2002-01793-mum-form 2(title page)-(complete)-(13-12-2002).pdf
in-pct-2002-01793-mum-form 2(title page)-(granted)-(5-3-2007).pdf
in-pct-2002-01793-mum-form 3(13-12-2002).pdf
in-pct-2002-01793-mum-form 3(9-9-2005).pdf
in-pct-2002-01793-mum-form 4(25-11-2005).pdf
in-pct-2002-01793-mum-form 5(13-12-2002).pdf
in-pct-2002-01793-mum-general power of attorney(25-3-2010).pdf
in-pct-2002-01793-mum-petition under rule 138(30-11-2005).pdf
in-pct-2002-01793-mum-power of authority(16-4-2003).pdf
in-pct-2002-01793-mum-power of authority(26-3-2003).pdf
in-pct-2002-01793-mum-power of authority(30-11-2005).pdf
in-pct-2002-01793-mum-ptition under rule 137(30-11-2005).pdf
in-pct-2002-01793-mum-ptition under rule 138(30-11-2005).pdf
| Patent Number | 204732 | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Indian Patent Application Number | IN/PCT/2002/01793/MUM | |||||||||||||||
| PG Journal Number | 25/2007 | |||||||||||||||
| Publication Date | 22-Jun-2007 | |||||||||||||||
| Grant Date | 05-Mar-2007 | |||||||||||||||
| Date of Filing | 13-Dec-2002 | |||||||||||||||
| Name of Patentee | MICROSOFT CORPORATION | |||||||||||||||
| Applicant Address | BUSINESS AT ONE MICROSOFT WAY, REDMOND, WASHINGTON 98052, UNITED STATES OF AMERICA | |||||||||||||||
Inventors:
|
||||||||||||||||
| PCT International Classification Number | H 04 L 29/06 | |||||||||||||||
| PCT International Application Number | PCT/US01/15223 | |||||||||||||||
| PCT International Filing date | 2001-05-11 | |||||||||||||||
PCT Conventions:
|
||||||||||||||||