US20020016828A1 - Web page rendering architecture - Google Patents
Web page rendering architecture Download PDFInfo
- Publication number
- US20020016828A1 US20020016828A1 US09/205,127 US20512798A US2002016828A1 US 20020016828 A1 US20020016828 A1 US 20020016828A1 US 20512798 A US20512798 A US 20512798A US 2002016828 A1 US2002016828 A1 US 2002016828A1
- Authority
- US
- United States
- Prior art keywords
- clips
- level
- level cache
- clip
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
Definitions
- This invention relates generally to web pages, and more particularly to a rendering architecture for web pages.
- Still other methodologies include reliance on database lookups and attempts to cache previous function calls and the content returned from those calls.
- any server-side code that relies upon database look-ups as part of their rendering process for web pages generally is also costly, and does not scale well.
- Previous attempts to cache function calls and the content returned therefrom have frequently been hampered by too much complexity and were generally not amenable to being scaled.
- a system includes a first server, a first-level cache, a second server, a second-level cache and one or more provider objects.
- the first server receives a request from a requester for a web page.
- the web page has a number of clips in an arrangement.
- the server determines the clips and the arrangement based on a key.
- the first-level cache which is at the first server, stores the clips from which the first server is to assemble the web page.
- the second server populates the first-level cache with any of the clips not yet stored there.
- the second-level cache which is at the second server, stores the clips from which the second server is to populate the first-level cache.
- the provider object or objects are at the second server, and populate the second-level cache with any of the clips not yet stored there.
- the key is based on information supplied by the user, such that the information returned is personalized based thereon.
- Content may be constantly updated from different sources, by interface with the provider objects.
- High performance is obtained in part by caching commonly used page fragments, which may be assembled in different ways depending on the key.
- the architecture is extensible and maintainable because suppliers of contents can easily be added or modified, by adding or modifying the provider objects.
- the modification of content by adding, changing, or removing suppliers of content does not typically require the redevelopment of other components of the system. Types of personalization also can be also be easily added or modified.
- the invention includes systems, methods, computers, and computer-readable media of varying scope. Besides the embodiments, advantages and aspects of the invention described here, the invention also includes other embodiments, advantages and aspects, as will become apparent by reading and studying the drawings and the following description.
- FIG. 1 shows a diagram of the hardware and operating environment in conjunction with which embodiments of the invention may be practiced
- FIG. 2 shows a block diagram of a system according to one embodiment of the invention
- FIG. 3 shows a block diagram of a part of a system according to one embodiment of the invention in more detail; and, FIG. 4 shows a flowchart of a method according to an embodiment of the invention.
- FIG. 1 a diagram of the hardware and operating environment in conjunction with which embodiments of the invention may be practiced is shown.
- the description of FIG. 1 is intended to provide a brief, general description of suitable computer hardware and a suitable computing environment in conjunction with which the invention may be implemented.
- the invention is described in the general context of computer-executable instructions, such as program modules, being executed by a computer, such as a personal computer.
- program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types.
- the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PC's, minicomputers, mainframe computers, and the like.
- the invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
- program modules may be located in both local and remote memory storage devices.
- the exemplary hardware and operating environment of FIG. 1 for implementing the invention includes a general purpose computing device in the form of a computer 20 , including a processing unit 21 , a system memory 22 , and a system bus 23 that operatively couples various system components include the system memory to the processing unit 21 .
- a processing unit 21 There may be only one or there may be more than one processing unit 21 , such that the processor of computer 20 comprises a single central-processing unit (CPU), or a plurality of processing units, commonly referred to as a parallel processing environment.
- the computer 20 may be a conventional computer, a distributed computer, or any other type of computer; the invention is not so limited.
- the system bus 23 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.
- the system memory may also be referred to as simply the memory, and includes read only memory (ROM) 24 and random access memory (RAM) 25 .
- ROM read only memory
- RAM random access memory
- a basic input/output system (BIOS) 26 containing the basic routines that help to transfer information between elements within the computer 20 , such as during start-up, is stored in ROM 24 .
- the computer 20 further includes a hard disk drive 27 for reading from and writing to a hard disk, not shown, a magnetic disk drive 28 for reading from or writing to a removable magnetic disk 29 , and an optical disk drive 30 for reading from or writing to a removable optical disk 31 such as a CD ROM or other optical media.
- a hard disk drive 27 for reading from and writing to a hard disk, not shown
- a magnetic disk drive 28 for reading from or writing to a removable magnetic disk 29
- an optical disk drive 30 for reading from or writing to a removable optical disk 31 such as a CD ROM or other optical media.
- the hard disk drive 27 , magnetic disk drive 28 , and optical disk drive 30 are connected to the system bus 23 by a hard disk drive interface 32 , a magnetic disk drive interface 33 , and an optical disk drive interface 34 , respectively.
- the drives and their associated computer-readable media provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for the computer 20 . It should be appreciated by those skilled in the art that any type of computer-readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memories (RAMs), read only memories (ROMs), and the like, may be used in the exemplary operating environment.
- a number of program modules may be stored on the hard disk, magnetic disk 29 , optical disk 31 , ROM 24 , or RAM 25 , including an operating system 35 , one or more application programs 36 , other program modules 37 , and program data 38 .
- a user may enter commands and information into the personal computer 20 through input devices such as a keyboard 40 and pointing device 42 .
- Other input devices may include a microphone, joystick, game pad, satellite dish, scanner, or the like.
- These and other input devices are often connected to the processing unit 21 through a serial port interface 46 that is coupled to the system bus, but may be connected by other interfaces, such as a parallel port, game port, or a universal serial bus (USB).
- a monitor 47 or other type of display device is also connected to the system bus 23 via an interface, such as a video adapter 48 .
- computers typically include other peripheral output devices (not shown), such as speakers and printers.
- the computer 20 may operate in a networked environment using logical connections to one or more remote computers, such as remote computer 49 . These logical connections are achieved by a communication device coupled to or a part of the computer 20 ; the invention is not limited to a particular type of communications device.
- the remote computer 49 may be another computer, a server, a router, a network PC, a client, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 20 , although only a memory storage device 50 has been illustrated in FIG. 1.
- the logical connections depicted in FIG. 1 include a local-area network (LAN) 51 and a wide-area network (WAN) 52 .
- LAN local-area network
- WAN wide-area network
- Such networking environments are commonplace in office networks, enterprise-wide computer networks, intranets and the Internal, which are all types of networks.
- the computer 20 When used in a LAN-networking environment, the computer 20 is connected to the local network 51 through a network interface or adapter 53 , which is one type of communications device.
- the computer 20 When used in a WAN-networking environment, the computer 20 typically includes a modem 54 , a type of communications device, or any other type of communications device for establishing communications over the wide area network 52 , such as the Internal.
- the modem 54 which may be internal or external, is connected to the system bus 23 via the serial port interface 46 .
- program modules depicted relative to the personal computer 20 may be stored in the remote memory storage device. It is appreciated that the network connections shown are exemplary and other means of and communications devices for establishing a communications link between the computers may be used.
- the computer in conjunction with which embodiments of the invention may be practiced may be a conventional computer, a distributed computer, or any other type of computer; the invention is not so limited.
- a computer typically includes one or more processing units as its processor, and a computer-readable medium such as a memory.
- the computer may also include a communications device such as a network adapter or a modem, so that it is able to communicatively couple other computers.
- the system includes a user browser 100 , a first server 102 , and a second server 104 .
- the first server 102 receives a request from the user browser 100 for a web page.
- the user browser 100 is thus a requester (the user of the browser 100 may also be considered the requester).
- the user browser 100 is connected to the first server 102 in one embodiment by an Internet technology, such as the Internet, an intranet, etc.
- the user browser 100 is a computer program or other technology that is able to display web pages, such as the Microsoft Internet Explorer browser.
- the web page requested by the user browser 100 is identified by a Universal Resource Locator (URL) address.
- the web page is made up of a number of HyperText Markup Language (HTML) clips, in a given arrangement.
- the first server 102 determines the clips and the arrangement for the web page based on a key identified in FIG. 2 as personalization 108 .
- the key is derived by the server 102 from a local file stored at the requester, as well as the web page requested by the requester.
- the local file may be what is known in the art as a cookie file, which is read by the browser 100 on the local PC (the requester), and sent to the server 102 in the cookie portion of an HTTP header, as part of a web page GET request, as known within the art. Furthermore, the web page requested by the requester is itself identified by its Universal Resource Locator (URL) address.
- the server 102 has an Internet Server Application Programming Interface (ISAPI) 106 and a first-level cache 110 .
- ISAPI Internet Server Application Programming Interface
- the ISAPI 106 based on the web page requested and the personalization 108 , assembles HTML clips (i.e., it determines the necessary HTML clips specified by the personalization 108 ) as stored in the first-level cache 110 according to the arrangement specified by the personalization 108 and the web page requested. As it receives the HTML clips, or in another embodiment once all the HTML clips have been retrieved, the server 102 returns them to the user browser 100 for display thereon. The server 102 may also return the completed web page.
- This personalization in one embodiment occurs as follows.
- the ISAPI 106 references a data structure in extensible Markup Language (XML) format that specifies different HTML clips for that web page.
- XML extensible Markup Language
- the cookie file stored by the user browser 100 determines which of those HTML clips are to be used to return to the user browser 100 .
- the XML data structures may be cached in the
- personalization data is retrieved from the cookie file, or in another embodiment a personalization identification (such as GUID, as known within the art), that enables the ISAPI 106 to retrieve the user's personalization data from a server-side store (as may be cached by the cache 110 or another cache that will be described).
- the personalization data is used to determine which categories and clips are shown on the custom page being built, the order in which categories and clips are displayed, and the contents of those clips that are personalized.
- a weather clip may display the local weather forecast, depending on the user's zip code.
- the clips are requested from the first-level cache 110 .
- the cache key contains the following information: the identification of the provider, and name value pair parameters that communicate sufficient information to the provider object so that it is able to generate the HTML clip.
- the XML description of the web pages makes the architecture of the invention in one embodiment easily extensible.
- the XML describes parameters and how to look them up for a given user request.
- This information is passed to one or more caches and in one embodiment to a provider object and possibly eventually to a provider object, which contain pre-formed HTML clips corresponding to the cache request. That is, the caches contain pre-formed HTML clips, while the provider objects generate these clips from HTML templates and raw data.
- changes in the XML allow the system to easily add or remove content providers, or change the personalization parameters being used for a given content provider.
- the first-level cache at the first server 102 thus stores the clips from which the first server 102 is to assemble the web page.
- the caching scheme is a high-performance distributed cache. Desirably, the caching scheme is efficient, such that search time decreased, the ability to handle higher peak load per machine is increased, and the cost per search is reduced (indicating high locality within the cache). Also desirably, the caching scheme is fast, robust (having a minimum number of external failures resulting in the failure of the cache), complete (such that all highly recurring query results are stored), current (no item stays in the cache longer than a given time limit, unless otherwise specified), intelligent (having flexible caching policies), and reusable (that is, scalable).
- the caching scheme is based on a threading model, such that multiple user threads are allowed.
- the caching scheme utilizes an indexing model known in the art as a direct-chained caching model; the cache content has a limited lifetime (record expiration model); the caching scheme is also based on a record access model providing for record protection (locking) when multiple threads add, read, delete and update index entries in parallel; and, the caching scheme utilizes data compression; the cache has very intensive heap memory use.
- the invention is not necessarily so limited, however.
- the second server 104 If a particular clip requested by the ISAPI 106 is not in the first-level cache 110 , the cache 110 requests the clip from the second server 104 .
- the second server 104 therefore populates the first-level cache with any of the clips not yet stored at the first-level cache.
- the second server 104 includes a second-level cache 112 , a third-level provider interface 114 , as well as one or more provider objects, such as a generic object 116 , a stock object 118 , and a weather object 120 .
- the second-level cache 112 stores the clips from which the second server 104 is to populate the first-level cache 110 of the first server 102 .
- the cache 112 provides a service that responds to requests from the server 102 when clips are requested that are not in the first-level cache 110 .
- the cache 112 then returns clips.
- the caching scheme is a high-performance distributed cache, as has been described. That is, desirably, the caching scheme is efficient, such that search time decreased, the ability to handle higher peak load per machine is increased, and the cost per search is reduced (indicating high locality within the cache).
- the caching scheme is fast, robust (having a minimum number of external failures resulting in the failure of the cache), complete (such that all highly recurring query results are stored), current (no item stays in the cache longer than a given time limit, unless otherwise specified), intelligent (having flexible caching policies), and reusable (that is, scalable).
- the caching scheme is based on a threading model, such that multiple user threads are allowed.
- the caching scheme utilizes an indexing model known in the art as a direct-chained caching model; the cache content has a limited lifetime (record expiration model); the caching scheme is also based on a record access model providing for record protection (locking) when multiple threads add, read, delete and update index entries in parallel; and, the caching scheme utilizes data compression; the cache has very intensive heap memory use.
- the cache 112 requests the clip from the provider interface 114 .
- the provider interface 114 maps the clip requested to the correct provider object.
- Each provider object at the second server 104 thus populates the second-level cache 112 with any of the clips not yet stored at the second-level cache 112 . Therefore, the interface 114 may direct the clip request to a generic object 116 , a stock object 118 , or a weather object 120 , in the embodiment of FIG. 2, although the invention is not necessarily so limited.
- a provider object returns the HTML clip requested to the provider interface 114 , the clip is stored in the second-level cache 112 , provided to and also stored in the first-level cache 110 , and ultimately provided to the ISAPI 106 . Therefore, when the ISAPI 106 requests an HTML clip, three situations may occur. If the cache 110 has the clip stored therein, it immediately returns the clip to the ISAPI 106 . If the cache 110 does not have the clip, but the cache 112 does, then the cache 112 returns the clip to the cache 110 , which stores the clip and returns it to the ISAPI 106 .
- the provider interface 114 obtains the clip from one of the provider objects, returns it to the cache 112 where the clip is stored, and the cache 112 provides it to the cache 110 , which also stores the clip and returns it to the ISAPI 106 .
- the provider interface 114 receives a message from a provider object that the content stored in the cache 112 is outdated, and the interface 114 removes the old information from the cache.
- a provider object tells the provider interface 114 which directories/files it wants to know about that may change. Then the provider interface 114 listens to file change notifications and signals each provider object if it previously told the provider interface 114 that it cares about a particular file. At this time, the provider object reinitializes itself and may indicate (if content truly has changed) to provider interface 114 that content has changed.
- the cache 112 then notifies the cache 110 of the first server 102 that the content needs to be updated, and cache 110 also removes the old information from the cache.
- this clip is generated by a provider object, and repopulated through the caches 112 and 110 .
- the second-level cache may periodically notify the first-level cache that one or more clips stored at the first level cache are outdated, such that they are deleted from the first-level cache.
- first server 102 may be considered part of a first level to receive a request from a requester for a web page having a plurality of clips in an arrangement, where the first level determines the clips and the arrangement based on a key, and caches the clips from which the web page is assembled.
- the second server 104 may be considered part of a second level to populate the first level with any of the clips not yet cached by the first level and to cache the clips from which the first level is populated.
- the system of an embodiment of the invention may be scalable and extensible in that there may be more than one provider object and/or parser, such that not all of the provider objects and/or parsers are present in the system when it is first configured.
- the later-added provider objects and/or parsers can be added to the system without requiring redevelopment or changing of the already present provider objects and/or parsers.
- the provider objects and parsers can be Component Object Model (COM) objects, although the invention is not so limited.
- COM Component Object Model
- FIG. 3 a part of a system according to an embodiment of the invention is shown in more detail.
- the second server 104 as in FIG. 2, is again shown, with constituent parts the second-level cache 112 , the provider interface 114 , and the provider objects 116 , 118 and 120 .
- Reference to FIG. 3 is made to describe the manner by which the objects 116 , 118 and 120 retrieve data and/or generate HTML clips, which are then provided to the interface 114 .
- the operation of the second server 104 , the second-level cache 112 , and the provider 114 in FIG. 3 is consistent with that as has been described in conjunction with FIG. 2.
- the provider objects 116 , 118 and 120 of FIG. 3 include a generic object 116 , and two particular objects, the stock object 118 and the weather object 120 .
- the invention is not necessarily limited to any given number of provider objects, nor a type of provider objects.
- the particular objects are specific objects particular to a given type of data from which a clip is generated.
- the provider objects utilize the cache-key, and generate the HTML clip corresponding to this key from data provided by the content fetcher 200 .
- this is accomplished with a mapping file, one or more files containing HTML fragments, and the data files delivered by the content fetcher 200 .
- the mapping file allows for the key to be mapped to the correct HTML files on disk without this mapping being built into the provider object itself, to support easy modification and extensibility without code redevelopment.
- provider objects may be restricted in how long they take to respond, since a user (requester) may have to wait while the clip is being built (e.g., a duration of four milliseconds or shorter).
- the generic object 116 uses in one embodiment a mapping file, HTML files, and text data files delivered by the content fetcher 200 .
- the generic object 116 is utilized for many content providers, which will be described.
- the mapping file provides sufficient flexibility for the object 116 to be used, for example, for all news headline providers, sports headline or sports score providers, as such providers are known within the art, and other content providers that have a small well-defined set of XML data files that can be merged into preauthored HTML fragments. Given the key, the object 116 is able to return the requested clip.
- the stock object 118 in one embodiment directly retrieves information from a financial information server, maintains an internal cache of at least some requested stock and securities data, and uses HTML files and data merging to produce HTML sub-clips for an individual stock quote.
- the XML file describes how then to assemble a provider header, a body of one or more stock sub-clips, and a provider footer, to maximize the cacheability of the stock data, given the large number of permutations that may be found in user stock lists.
- the stock object does not use the fetcher.
- the weather object 120 in one embodiment uses a mapping file, HTML files, and text data files delivered by the content fetcher 200 . Thus, given a requestor's location (for example, by zip code), the object 120 is able to return a clip containing a weather forecast for that area.
- the provider objects interface with the content fetcher 200 via the file system 202 .
- the file system 202 is the storage space for the HTML, text and data files, such as a hard drive of a computer, although the invention is not so limited.
- the content fetcher 200 provides the provider objects with data from which any of the clips not yet stored at the second-level cache 112 are generated. It also supplies updates to content for clips that already have been stored at the second-level cache 112 and first level cache 110 .
- the content fetcher includes parsers 204 , a fetcher 206 , and a fetcher database 208 .
- the parsers 204 are in one embodiment objects, which parse the information retrieved by the fetcher 206 , and generate text data files and/or HTML files to be stored in the file system 202 for retrieval and use by the provider objects.
- the parsers 204 may be generic or specialized. Furthermore, parsers may be added to extend the system without any other components requiring redevelopment, which is an advantage of the invention.
- the fetcher 206 retrieves information from the external content providers 210 based on a set schedule set in the database 208 , where the schedule in one embodiment is independent of requests from provider objects.
- the fetcher 206 may determine based on the fetcher database 208 that a previously provided HTML clip now stored in one of the caches is out-of-date, and will fetch new data from an external content provider, providing (or, pushing) this information to the appropriate provider object via the appropriate parser 204 and the file system 202 .
- Each of the external content providers 210 can in one embodiment be a different web site providing the raw data fetched by the fetcher 206 and parsed by the parser 204 . Each of these content providers is thus to provide the content fetcher 200 with a specific part of the data from which clips not yet stored at the second-level cache (or, outdated clips) are generated.
- a third level may be considered that includes at least one of the provider interface 114 , the provider objects 116 , 118 and 120 , the content fetcher 200 , and the external content providers 210 .
- the computerized method is desirably realized at least in part as one or more programs running on a computer—that is, as a program executed from a computer-readable medium such as a memory by a processor of a computer.
- the programs are desirably storable on a computer-readable medium such as a floppy disk or a CD-ROM, for distribution and installation and execution on another (suitably equipped) computer.
- a user web browser i.e., a requester
- requests a desired web page In 400 , it is determined whether any personalization data exists for this requester. For example, in an embodiment of the invention where such data is stored in cookie files on the requester computer, the option exists to turn off cookie files, such that no personalization information can be stored. In such an instance, a static default web page is returned to the requester in 406 , and the method is finished in 408 .
- 406 and 408 are proceeded to in the case of a new user, who has not yet had an opportunity to personalize the service, or in the case of a returning user, who has decided not to personalize the service.
- all the clips necessary to build the web page are assembled according to an arrangement.
- a key based on a local file stored at the requester as well as the desired web page requested by the requester is derived, and the necessary plurality of clips and the arrangement thereof is determined based on the key.
- For each of the clips first in 412 , it is determined whether the clip is stored in a first level cache. If it is, then in 414 the clip is returned to the requester, positioned as determined by the arrangement. If it is the last clip, then the method proceeds from 416 to 418 , where the method ends, until the requester requests another web page at 400 .
- a clip is not in the first-level cache, then in 422 it is determined whether the clip is stored in a second-level cache. If it is, then the clip is inserted into the first level cache (not specifically shown in the figure), and the method proceeds from 422 to 414 , where the clip is written out to the requester browser, as has been described. If the clip is not in the second-level cache, however, then in 424 the clip is obtained, for example, from a third level including a provider object. This is accomplished by the provider building the HTML clip in 426 from data identified in FIG. 4 as 428 . The clip is then inserted into both the first-level and the second-level cache, and the clip is written out to the requester browser in 414 , as has been described.
Abstract
Description
- This invention relates generally to web pages, and more particularly to a rendering architecture for web pages.
- BACKGROUND OF THE INVENTION
- With the growing popularity of the Internet and Internet-type technologies such as intranets, there has come a realization that users are interested in receiving personalized information via these technologies. For example, whereas before a user may have requested a web page from a web site such as http://www.msn.com that may have returned the same information regardless of the identification of the user, now the user may desire more specific information. For example, a user may desire the information returned from a given weather page to be relevant to the user's location. As another example, a user may desire that the information returned from a technical support page be relevant to only the applications installed on the user's computer.
- Delivery of personalized web pages by a web site generally requires other considerations for the architecture of web site as compared to non-personalized web pages. For example, the rendering of personalized web pages on the Internet desirably needs to be fast and scalable, like other web sites. However, potentially unlike other web sites, it should also desirably be easy to modify the look or presentation of the web site daily or weekly. In addition, it should desirably be easy to modify the look or presentation based on the identification of the user. This makes the development of such web site architectures more difficult.
- Current Internet or intranet services that intend to provide personalized and personally relevant content to users usually use server-side scripting, server-side objects (such as what are known as Common Gateway Interface (CGI) programs), as well as other methodologies. However, server-side scripting is expensive computationally speaking, because of run-time parsing and interpretation that must be performed for every request. In addition, objects are often instantiated and released repeatedly, which reduces performance, and the code itself is intermingled with display elements in HyperText Markup Language (HTML) format, which makes maintenance more difficult.
- Still other methodologies include reliance on database lookups and attempts to cache previous function calls and the content returned from those calls. However, any server-side code that relies upon database look-ups as part of their rendering process for web pages generally is also costly, and does not scale well. Previous attempts to cache function calls and the content returned therefrom have frequently been hampered by too much complexity and were generally not amenable to being scaled.
- For these and other reasons, there is a need for the present invention.
- The invention provides for an architecture for rendering web pages. In one embodiment, a system includes a first server, a first-level cache, a second server, a second-level cache and one or more provider objects. The first server receives a request from a requester for a web page. The web page has a number of clips in an arrangement. The server determines the clips and the arrangement based on a key. The first-level cache, which is at the first server, stores the clips from which the first server is to assemble the web page. The second server populates the first-level cache with any of the clips not yet stored there. The second-level cache, which is at the second server, stores the clips from which the second server is to populate the first-level cache. The provider object or objects are at the second server, and populate the second-level cache with any of the clips not yet stored there.
- The invention provides for advantages not found in the prior art. In one embodiment, the key is based on information supplied by the user, such that the information returned is personalized based thereon. Content may be constantly updated from different sources, by interface with the provider objects. High performance is obtained in part by caching commonly used page fragments, which may be assembled in different ways depending on the key. The architecture is extensible and maintainable because suppliers of contents can easily be added or modified, by adding or modifying the provider objects. Furthermore, the modification of content by adding, changing, or removing suppliers of content does not typically require the redevelopment of other components of the system. Types of personalization also can be also be easily added or modified.
- The invention includes systems, methods, computers, and computer-readable media of varying scope. Besides the embodiments, advantages and aspects of the invention described here, the invention also includes other embodiments, advantages and aspects, as will become apparent by reading and studying the drawings and the following description.
- FIG. 1 shows a diagram of the hardware and operating environment in conjunction with which embodiments of the invention may be practiced;
- FIG. 2 shows a block diagram of a system according to one embodiment of the invention;
- FIG. 3 shows a block diagram of a part of a system according to one embodiment of the invention in more detail; and, FIG. 4 shows a flowchart of a method according to an embodiment of the invention.
- In the following detailed description of exemplary embodiments of the invention, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration specific exemplary embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that logical, mechanical, electrical and other changes may be made without departing from the spirit or scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims.
- The detailed description is divided into four sections. In the first section, the hardware and the operating environment in conjunction with which embodiments of the invention may be practiced are described. In the second section, a system of one embodiment of the invention is presented. In the third section, a method in accordance with an embodiment of the invention is described. Finally, in the fourth section, a conclusion of the detailed description is provided.
- Referring to FIG. 1, a diagram of the hardware and operating environment in conjunction with which embodiments of the invention may be practiced is shown. The description of FIG. 1 is intended to provide a brief, general description of suitable computer hardware and a suitable computing environment in conjunction with which the invention may be implemented. Although not required, the invention is described in the general context of computer-executable instructions, such as program modules, being executed by a computer, such as a personal computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types.
- Moreover, those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PC's, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
- The exemplary hardware and operating environment of FIG. 1 for implementing the invention includes a general purpose computing device in the form of a
computer 20, including aprocessing unit 21, asystem memory 22, and asystem bus 23 that operatively couples various system components include the system memory to theprocessing unit 21. There may be only one or there may be more than oneprocessing unit 21, such that the processor ofcomputer 20 comprises a single central-processing unit (CPU), or a plurality of processing units, commonly referred to as a parallel processing environment. Thecomputer 20 may be a conventional computer, a distributed computer, or any other type of computer; the invention is not so limited. - The
system bus 23 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. The system memory may also be referred to as simply the memory, and includes read only memory (ROM) 24 and random access memory (RAM) 25. A basic input/output system (BIOS) 26, containing the basic routines that help to transfer information between elements within thecomputer 20, such as during start-up, is stored inROM 24. Thecomputer 20 further includes ahard disk drive 27 for reading from and writing to a hard disk, not shown, amagnetic disk drive 28 for reading from or writing to a removablemagnetic disk 29, and anoptical disk drive 30 for reading from or writing to a removableoptical disk 31 such as a CD ROM or other optical media. - The
hard disk drive 27,magnetic disk drive 28, andoptical disk drive 30 are connected to thesystem bus 23 by a harddisk drive interface 32, a magneticdisk drive interface 33, and an opticaldisk drive interface 34, respectively. The drives and their associated computer-readable media provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for thecomputer 20. It should be appreciated by those skilled in the art that any type of computer-readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memories (RAMs), read only memories (ROMs), and the like, may be used in the exemplary operating environment. - A number of program modules may be stored on the hard disk,
magnetic disk 29,optical disk 31,ROM 24, orRAM 25, including anoperating system 35, one ormore application programs 36,other program modules 37, andprogram data 38. A user may enter commands and information into thepersonal computer 20 through input devices such as akeyboard 40 andpointing device 42. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to theprocessing unit 21 through aserial port interface 46 that is coupled to the system bus, but may be connected by other interfaces, such as a parallel port, game port, or a universal serial bus (USB). Amonitor 47 or other type of display device is also connected to thesystem bus 23 via an interface, such as avideo adapter 48. In addition to the monitor, computers typically include other peripheral output devices (not shown), such as speakers and printers. - The
computer 20 may operate in a networked environment using logical connections to one or more remote computers, such asremote computer 49. These logical connections are achieved by a communication device coupled to or a part of thecomputer 20; the invention is not limited to a particular type of communications device. Theremote computer 49 may be another computer, a server, a router, a network PC, a client, a peer device or other common network node, and typically includes many or all of the elements described above relative to thecomputer 20, although only amemory storage device 50 has been illustrated in FIG. 1. The logical connections depicted in FIG. 1 include a local-area network (LAN) 51 and a wide-area network (WAN) 52. Such networking environments are commonplace in office networks, enterprise-wide computer networks, intranets and the Internal, which are all types of networks. - When used in a LAN-networking environment, the
computer 20 is connected to thelocal network 51 through a network interface oradapter 53, which is one type of communications device. When used in a WAN-networking environment, thecomputer 20 typically includes amodem 54, a type of communications device, or any other type of communications device for establishing communications over thewide area network 52, such as the Internal. Themodem 54, which may be internal or external, is connected to thesystem bus 23 via theserial port interface 46. In a networked environment, program modules depicted relative to thepersonal computer 20, or portions thereof, may be stored in the remote memory storage device. It is appreciated that the network connections shown are exemplary and other means of and communications devices for establishing a communications link between the computers may be used. - The hardware and operating environment in conjunction with which embodiments of the invention may be practiced has been described. The computer in conjunction with which embodiments of the invention may be practiced may be a conventional computer, a distributed computer, or any other type of computer; the invention is not so limited. Such a computer typically includes one or more processing units as its processor, and a computer-readable medium such as a memory. The computer may also include a communications device such as a network adapter or a modem, so that it is able to communicatively couple other computers.
- In this section of the detailed description, a description of a system, according to an embodiment of the invention is provided. The description is provided by reference to FIG. 2 and FIG. 3. Referring now to FIG. 2, a system according to an embodiment of the invention is shown. The system includes a
user browser 100, afirst server 102, and asecond server 104. Thefirst server 102 receives a request from theuser browser 100 for a web page. Theuser browser 100 is thus a requester (the user of thebrowser 100 may also be considered the requester). Theuser browser 100 is connected to thefirst server 102 in one embodiment by an Internet technology, such as the Internet, an intranet, etc. Theuser browser 100 is a computer program or other technology that is able to display web pages, such as the Microsoft Internet Explorer browser. - The web page requested by the
user browser 100 is identified by a Universal Resource Locator (URL) address. In one embodiment, the web page is made up of a number of HyperText Markup Language (HTML) clips, in a given arrangement. Thefirst server 102 determines the clips and the arrangement for the web page based on a key identified in FIG. 2 aspersonalization 108. In one embodiment, the key is derived by theserver 102 from a local file stored at the requester, as well as the web page requested by the requester. The local file may be what is known in the art as a cookie file, which is read by thebrowser 100 on the local PC (the requester), and sent to theserver 102 in the cookie portion of an HTTP header, as part of a web page GET request, as known within the art. Furthermore, the web page requested by the requester is itself identified by its Universal Resource Locator (URL) address. Theserver 102 has an Internet Server Application Programming Interface (ISAPI) 106 and a first-level cache 110. TheISAPI 106, based on the web page requested and thepersonalization 108, assembles HTML clips (i.e., it determines the necessary HTML clips specified by the personalization 108) as stored in the first-level cache 110 according to the arrangement specified by thepersonalization 108 and the web page requested. As it receives the HTML clips, or in another embodiment once all the HTML clips have been retrieved, theserver 102 returns them to theuser browser 100 for display thereon. Theserver 102 may also return the completed web page. - This personalization in one embodiment occurs as follows. Depending on the URL address of the web page requested, the
ISAPI 106 references a data structure in extensible Markup Language (XML) format that specifies different HTML clips for that web page. Furthermore, the cookie file stored by theuser browser 100 determines which of those HTML clips are to be used to return to theuser browser 100. The XML data structures may be cached in the - Therefore, personalization data is retrieved from the cookie file, or in another embodiment a personalization identification (such as GUID, as known within the art), that enables the
ISAPI 106 to retrieve the user's personalization data from a server-side store (as may be cached by thecache 110 or another cache that will be described). The personalization data is used to determine which categories and clips are shown on the custom page being built, the order in which categories and clips are displayed, and the contents of those clips that are personalized. Thus, a weather clip may display the local weather forecast, depending on the user's zip code. Based on the cache-key built using a parameter description contained in the XML data structure (the specific XML data structure used based on the web page URL), and the personalization data, the clips are requested from the first-level cache 110. In one embodiment, the cache key contains the following information: the identification of the provider, and name value pair parameters that communicate sufficient information to the provider object so that it is able to generate the HTML clip. The XML description of the web pages makes the architecture of the invention in one embodiment easily extensible. The XML describes parameters and how to look them up for a given user request. This information is passed to one or more caches and in one embodiment to a provider object and possibly eventually to a provider object, which contain pre-formed HTML clips corresponding to the cache request. That is, the caches contain pre-formed HTML clips, while the provider objects generate these clips from HTML templates and raw data. Thus, changes in the XML allow the system to easily add or remove content providers, or change the personalization parameters being used for a given content provider. - The first-level cache at the
first server 102 thus stores the clips from which thefirst server 102 is to assemble the web page. In one embodiment, the caching scheme is a high-performance distributed cache. Desirably, the caching scheme is efficient, such that search time decreased, the ability to handle higher peak load per machine is increased, and the cost per search is reduced (indicating high locality within the cache). Also desirably, the caching scheme is fast, robust (having a minimum number of external failures resulting in the failure of the cache), complete (such that all highly recurring query results are stored), current (no item stays in the cache longer than a given time limit, unless otherwise specified), intelligent (having flexible caching policies), and reusable (that is, scalable). - In one particular embodiment, the caching scheme is based on a threading model, such that multiple user threads are allowed. In addition, the caching scheme utilizes an indexing model known in the art as a direct-chained caching model; the cache content has a limited lifetime (record expiration model); the caching scheme is also based on a record access model providing for record protection (locking) when multiple threads add, read, delete and update index entries in parallel; and, the caching scheme utilizes data compression; the cache has very intensive heap memory use. The invention is not necessarily so limited, however.
- If a particular clip requested by the
ISAPI 106 is not in the first-level cache 110, thecache 110 requests the clip from thesecond server 104. Thesecond server 104 therefore populates the first-level cache with any of the clips not yet stored at the first-level cache. Thesecond server 104 includes a second-level cache 112, a third-level provider interface 114, as well as one or more provider objects, such as ageneric object 116, astock object 118, and aweather object 120. - The second-
level cache 112 stores the clips from which thesecond server 104 is to populate the first-level cache 110 of thefirst server 102. Thecache 112 provides a service that responds to requests from theserver 102 when clips are requested that are not in the first-level cache 110. Thecache 112 then returns clips. In one embodiment, the caching scheme is a high-performance distributed cache, as has been described. That is, desirably, the caching scheme is efficient, such that search time decreased, the ability to handle higher peak load per machine is increased, and the cost per search is reduced (indicating high locality within the cache). Also desirably, the caching scheme is fast, robust (having a minimum number of external failures resulting in the failure of the cache), complete (such that all highly recurring query results are stored), current (no item stays in the cache longer than a given time limit, unless otherwise specified), intelligent (having flexible caching policies), and reusable (that is, scalable). - In one particular embodiment, the caching scheme is based on a threading model, such that multiple user threads are allowed. In addition, the caching scheme utilizes an indexing model known in the art as a direct-chained caching model; the cache content has a limited lifetime (record expiration model); the caching scheme is also based on a record access model providing for record protection (locking) when multiple threads add, read, delete and update index entries in parallel; and, the caching scheme utilizes data compression; the cache has very intensive heap memory use.
- However, if a particular clip requested by the
first server 102 is not in the second-level cache 112, either, then thecache 112 requests the clip from theprovider interface 114. Theprovider interface 114 maps the clip requested to the correct provider object. Each provider object at thesecond server 104 thus populates the second-level cache 112 with any of the clips not yet stored at the second-level cache 112. Therefore, theinterface 114 may direct the clip request to ageneric object 116, astock object 118, or aweather object 120, in the embodiment of FIG. 2, although the invention is not necessarily so limited. - Once a provider object returns the HTML clip requested to the
provider interface 114, the clip is stored in the second-level cache 112, provided to and also stored in the first-level cache 110, and ultimately provided to theISAPI 106. Therefore, when theISAPI 106 requests an HTML clip, three situations may occur. If thecache 110 has the clip stored therein, it immediately returns the clip to theISAPI 106. If thecache 110 does not have the clip, but thecache 112 does, then thecache 112 returns the clip to thecache 110, which stores the clip and returns it to theISAPI 106. If neither cache has the clip, then theprovider interface 114 obtains the clip from one of the provider objects, returns it to thecache 112 where the clip is stored, and thecache 112 provides it to thecache 110, which also stores the clip and returns it to theISAPI 106. - In some situations, there is a need for the content (that is, the HTML clips) as stored in the
cache 110 and thecache 112 to be updated. This is in one embodiment provider-object driven. Thus, theprovider interface 114 receives a message from a provider object that the content stored in thecache 112 is outdated, and theinterface 114 removes the old information from the cache. - In another embodiment, a provider object tells the
provider interface 114 which directories/files it wants to know about that may change. Then theprovider interface 114 listens to file change notifications and signals each provider object if it previously told theprovider interface 114 that it cares about a particular file. At this time, the provider object reinitializes itself and may indicate (if content truly has changed) toprovider interface 114 that content has changed. - In either embodiment, the
cache 112 then notifies thecache 110 of thefirst server 102 that the content needs to be updated, andcache 110 also removes the old information from the cache. Thus, the next time this clip is requested, it is generated by a provider object, and repopulated through thecaches - Scalability is provided by embodiments of the invention. While only one
first server 102 and onesecond server 104 are shown in FIG. 2, there may be manyfirst servers 102 to a givensecond server 104. There may also be manysecond servers 104. In this manner, servers may be added as needed for performance and other reasons. Thefirst server 102 may be considered part of a first level to receive a request from a requester for a web page having a plurality of clips in an arrangement, where the first level determines the clips and the arrangement based on a key, and caches the clips from which the web page is assembled. Thesecond server 104 may be considered part of a second level to populate the first level with any of the clips not yet cached by the first level and to cache the clips from which the first level is populated. - Furthermore, scalability and extensibility is provided by the ability to add new provider objects, and new parsers in the content fetcher for those provider objects, without requiring any of the already existing provider objects and/or parsers to be rewritten in any manner. This is an advantage of the invention, insofar as modification of a given web personalization architecture can be made later—thus, the initial architecture does not have to be rigidly defined a priori. In other words, the system of an embodiment of the invention may be scalable and extensible in that there may be more than one provider object and/or parser, such that not all of the provider objects and/or parsers are present in the system when it is first configured. The later-added provider objects and/or parsers can be added to the system without requiring redevelopment or changing of the already present provider objects and/or parsers. In one embodiment, the provider objects and parsers can be Component Object Model (COM) objects, although the invention is not so limited.
- Referring next to FIG. 3, a part of a system according to an embodiment of the invention is shown in more detail. The
second server 104, as in FIG. 2, is again shown, with constituent parts the second-level cache 112, theprovider interface 114, and the provider objects 116, 118 and 120. Reference to FIG. 3 is made to describe the manner by which theobjects interface 114. The operation of thesecond server 104, the second-level cache 112, and theprovider 114 in FIG. 3 is consistent with that as has been described in conjunction with FIG. 2. - The provider objects116, 118 and 120 of FIG. 3 include a
generic object 116, and two particular objects, thestock object 118 and theweather object 120. The invention is not necessarily limited to any given number of provider objects, nor a type of provider objects. The particular objects are specific objects particular to a given type of data from which a clip is generated. - The provider objects utilize the cache-key, and generate the HTML clip corresponding to this key from data provided by the
content fetcher 200. In one embodiment, this is accomplished with a mapping file, one or more files containing HTML fragments, and the data files delivered by thecontent fetcher 200. The mapping file allows for the key to be mapped to the correct HTML files on disk without this mapping being built into the provider object itself, to support easy modification and extensibility without code redevelopment. In one embodiment, provider objects may be restricted in how long they take to respond, since a user (requester) may have to wait while the clip is being built (e.g., a duration of four milliseconds or shorter). - The
generic object 116 uses in one embodiment a mapping file, HTML files, and text data files delivered by thecontent fetcher 200. Thegeneric object 116 is utilized for many content providers, which will be described. The mapping file provides sufficient flexibility for theobject 116 to be used, for example, for all news headline providers, sports headline or sports score providers, as such providers are known within the art, and other content providers that have a small well-defined set of XML data files that can be merged into preauthored HTML fragments. Given the key, theobject 116 is able to return the requested clip. - The
stock object 118 in one embodiment directly retrieves information from a financial information server, maintains an internal cache of at least some requested stock and securities data, and uses HTML files and data merging to produce HTML sub-clips for an individual stock quote. The XML file describes how then to assemble a provider header, a body of one or more stock sub-clips, and a provider footer, to maximize the cacheability of the stock data, given the large number of permutations that may be found in user stock lists. In one embodiment, the stock object does not use the fetcher. Theweather object 120 in one embodiment uses a mapping file, HTML files, and text data files delivered by thecontent fetcher 200. Thus, given a requestor's location (for example, by zip code), theobject 120 is able to return a clip containing a weather forecast for that area. - Thus, in the general case, the provider objects interface with the
content fetcher 200 via thefile system 202. Thefile system 202 is the storage space for the HTML, text and data files, such as a hard drive of a computer, although the invention is not so limited. Thecontent fetcher 200 provides the provider objects with data from which any of the clips not yet stored at the second-level cache 112 are generated. It also supplies updates to content for clips that already have been stored at the second-level cache 112 andfirst level cache 110. The content fetcher includesparsers 204, afetcher 206, and afetcher database 208. - The
parsers 204 are in one embodiment objects, which parse the information retrieved by thefetcher 206, and generate text data files and/or HTML files to be stored in thefile system 202 for retrieval and use by the provider objects. Theparsers 204 may be generic or specialized. Furthermore, parsers may be added to extend the system without any other components requiring redevelopment, which is an advantage of the invention. Thefetcher 206 retrieves information from theexternal content providers 210 based on a set schedule set in thedatabase 208, where the schedule in one embodiment is independent of requests from provider objects. Thefetcher 206 may determine based on thefetcher database 208 that a previously provided HTML clip now stored in one of the caches is out-of-date, and will fetch new data from an external content provider, providing (or, pushing) this information to the appropriate provider object via theappropriate parser 204 and thefile system 202. - Each of the
external content providers 210 can in one embodiment be a different web site providing the raw data fetched by thefetcher 206 and parsed by theparser 204. Each of these content providers is thus to provide thecontent fetcher 200 with a specific part of the data from which clips not yet stored at the second-level cache (or, outdated clips) are generated. In one embodiment of the invention, a third level may be considered that includes at least one of theprovider interface 114, the provider objects 116, 118 and 120, thecontent fetcher 200, and theexternal content providers 210. - In this section of the detailed description, methods according to an embodiment of the invention is presented. This description is provided in reference to FIG. 4. The computerized method is desirably realized at least in part as one or more programs running on a computer—that is, as a program executed from a computer-readable medium such as a memory by a processor of a computer. The programs are desirably storable on a computer-readable medium such as a floppy disk or a CD-ROM, for distribution and installation and execution on another (suitably equipped) computer.
- Referring now to FIG. 4, a method according to an embodiment of the invention is shown. In400, a user web browser (i.e., a requester) requests a desired web page. In 402, it is determined whether any personalization data exists for this requester. For example, in an embodiment of the invention where such data is stored in cookie files on the requester computer, the option exists to turn off cookie files, such that no personalization information can be stored. In such an instance, a static default web page is returned to the requester in 406, and the method is finished in 408. Furthermore, 406 and 408 are proceeded to in the case of a new user, who has not yet had an opportunity to personalize the service, or in the case of a returning user, who has decided not to personalize the service. In 410, all the clips necessary to build the web page are assembled according to an arrangement. Thus, a key based on a local file stored at the requester as well as the desired web page requested by the requester is derived, and the necessary plurality of clips and the arrangement thereof is determined based on the key. For each of the clips, first in 412, it is determined whether the clip is stored in a first level cache. If it is, then in 414 the clip is returned to the requester, positioned as determined by the arrangement. If it is the last clip, then the method proceeds from 416 to 418, where the method ends, until the requester requests another web page at 400.
- If, however, a clip is not in the first-level cache, then in422 it is determined whether the clip is stored in a second-level cache. If it is, then the clip is inserted into the first level cache (not specifically shown in the figure), and the method proceeds from 422 to 414, where the clip is written out to the requester browser, as has been described. If the clip is not in the second-level cache, however, then in 424 the clip is obtained, for example, from a third level including a provider object. This is accomplished by the provider building the HTML clip in 426 from data identified in FIG. 4 as 428. The clip is then inserted into both the first-level and the second-level cache, and the clip is written out to the requester browser in 414, as has been described.
- An architecture for rendering web pages has been described. Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement which is calculated to achieve the same purpose may be substituted for the specific embodiments shown. This application is intended to cover any adaptations or variations of the present invention. Therefore, it is manifestly intended that this invention be limited only by the following claims and equivalents thereof.
Claims (21)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/205,127 US6345292B1 (en) | 1998-12-03 | 1998-12-03 | Web page rendering architecture |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/205,127 US6345292B1 (en) | 1998-12-03 | 1998-12-03 | Web page rendering architecture |
Publications (2)
Publication Number | Publication Date |
---|---|
US6345292B1 US6345292B1 (en) | 2002-02-05 |
US20020016828A1 true US20020016828A1 (en) | 2002-02-07 |
Family
ID=22760911
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/205,127 Expired - Lifetime US6345292B1 (en) | 1998-12-03 | 1998-12-03 | Web page rendering architecture |
Country Status (1)
Country | Link |
---|---|
US (1) | US6345292B1 (en) |
Cited By (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020152197A1 (en) * | 2001-03-01 | 2002-10-17 | Stocker Jeffrey A. | Automatic generation of personal homepages for a sales force |
US20020188694A1 (en) * | 2001-06-07 | 2002-12-12 | Allen Yu | Cached enabled implicit personalization system and method |
US20030014439A1 (en) * | 2001-06-20 | 2003-01-16 | International Business Machines Corporation | Defining a markup language representation for state chart data |
US20030187935A1 (en) * | 2001-12-19 | 2003-10-02 | International Business Machines Corporation | Method and system for fragment linking and fragment caching |
US20030188021A1 (en) * | 2001-12-19 | 2003-10-02 | International Business Machines Corporation | Method and system for processing multiple fragment requests in a single message |
US20030191812A1 (en) * | 2001-12-19 | 2003-10-09 | International Business Machines Corporation | Method and system for caching role-specific fragments |
US7171470B2 (en) | 2003-02-20 | 2007-01-30 | International Business Machines Corporation | Grid service scheduling of related services using heuristics |
US20080134083A1 (en) * | 2006-11-30 | 2008-06-05 | Microsoft Corporation | Rendering document views with supplemental information content |
US7426534B2 (en) | 2001-12-19 | 2008-09-16 | International Business Machines Corporation | Method and system for caching message fragments using an expansion attribute in a fragment link tag |
US20090055727A1 (en) * | 2005-11-18 | 2009-02-26 | Kapow Technologies A/S | Method of performing web-clipping, a web-clipping server and a system for web-clipping |
US20090254867A1 (en) * | 2008-04-03 | 2009-10-08 | Microsoft Corporation | Zoom for annotatable margins |
US20090265420A1 (en) * | 2006-05-15 | 2009-10-22 | Kapow Technologies R & D A/S | Method of rendering at least one element in a client browser |
US20090307618A1 (en) * | 2008-06-05 | 2009-12-10 | Microsoft Corporation | Annotate at multiple levels |
US20100121983A1 (en) * | 1999-05-25 | 2010-05-13 | Realnetworks, Inc. | System and method for providing update information |
US8260845B1 (en) | 2007-11-21 | 2012-09-04 | Appcelerator, Inc. | System and method for auto-generating JavaScript proxies and meta-proxies |
US8285813B1 (en) | 2007-12-05 | 2012-10-09 | Appcelerator, Inc. | System and method for emulating different user agents on a server |
US8291079B1 (en) | 2008-06-04 | 2012-10-16 | Appcelerator, Inc. | System and method for developing, deploying, managing and monitoring a web application in a single environment |
US8335982B1 (en) | 2007-12-05 | 2012-12-18 | Appcelerator, Inc. | System and method for binding a document object model through JavaScript callbacks |
US8527860B1 (en) | 2007-12-04 | 2013-09-03 | Appcelerator, Inc. | System and method for exposing the dynamic web server-side |
US8566807B1 (en) | 2007-11-23 | 2013-10-22 | Appcelerator, Inc. | System and method for accessibility of document object model and JavaScript by other platforms |
US20130346474A1 (en) * | 2012-06-21 | 2013-12-26 | International Business Machines Corporation | Web storage optimization |
US8639743B1 (en) | 2007-12-05 | 2014-01-28 | Appcelerator, Inc. | System and method for on-the-fly rewriting of JavaScript |
US8719451B1 (en) | 2007-11-23 | 2014-05-06 | Appcelerator, Inc. | System and method for on-the-fly, post-processing document object model manipulation |
US8756579B1 (en) | 2007-12-03 | 2014-06-17 | Appcelerator, Inc. | Client-side and server-side unified validation |
US8806431B1 (en) | 2007-12-03 | 2014-08-12 | Appecelerator, Inc. | Aspect oriented programming |
US8819539B1 (en) | 2007-12-03 | 2014-08-26 | Appcelerator, Inc. | On-the-fly rewriting of uniform resource locators in a web-page |
US8880678B1 (en) | 2008-06-05 | 2014-11-04 | Appcelerator, Inc. | System and method for managing and monitoring a web application using multiple cloud providers |
US8892684B2 (en) | 2012-05-25 | 2014-11-18 | Microsoft Corporation | Dynamic selection of resources for compression in a content delivery network |
US8914774B1 (en) | 2007-11-15 | 2014-12-16 | Appcelerator, Inc. | System and method for tagging code to determine where the code runs |
US8938491B1 (en) | 2007-12-04 | 2015-01-20 | Appcelerator, Inc. | System and method for secure binding of client calls and server functions |
US8954989B1 (en) | 2007-11-19 | 2015-02-10 | Appcelerator, Inc. | Flexible, event-driven JavaScript server architecture |
US8954553B1 (en) | 2008-11-04 | 2015-02-10 | Appcelerator, Inc. | System and method for developing, deploying, managing and monitoring a web application in a single environment |
US9122650B1 (en) | 2007-11-14 | 2015-09-01 | Appcelerator, Inc. | Web server based on the same paradigms as web clients |
US9195638B2 (en) | 2010-07-12 | 2015-11-24 | Alibaba Group Holding Limited | Method and apparatus of processing nested fragment caching of a web page |
US9282137B2 (en) | 2012-05-25 | 2016-03-08 | Microsoft Technology Licensing, Llc | Dynamic package creation for predictive page load optimization |
US9633112B2 (en) | 2000-03-31 | 2017-04-25 | Kapow Software | Method of retrieving attributes from at least two data sources |
US9781135B2 (en) | 2014-06-20 | 2017-10-03 | Microsoft Technology Licensing, Llc | Intelligent web page content blocking |
Families Citing this family (56)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7249328B1 (en) * | 1999-05-21 | 2007-07-24 | E-Numerate Solutions, Inc. | Tree view for reusable data markup language |
US7650355B1 (en) * | 1999-05-21 | 2010-01-19 | E-Numerate Solutions, Inc. | Reusable macro markup language |
US9262384B2 (en) | 1999-05-21 | 2016-02-16 | E-Numerate Solutions, Inc. | Markup language system, method, and computer program product |
US9262383B2 (en) | 1999-05-21 | 2016-02-16 | E-Numerate Solutions, Inc. | System, method, and computer program product for processing a markup document |
US9268748B2 (en) | 1999-05-21 | 2016-02-23 | E-Numerate Solutions, Inc. | System, method, and computer program product for outputting markup language documents |
US7343412B1 (en) * | 1999-06-24 | 2008-03-11 | International Business Machines Corporation | Method for maintaining and managing dynamic web pages stored in a system cache and referenced objects cached in other data stores |
US6578000B1 (en) * | 1999-09-03 | 2003-06-10 | Cisco Technology, Inc. | Browser-based arrangement for developing voice enabled web applications using extensible markup language documents |
US6691176B1 (en) * | 1999-11-04 | 2004-02-10 | Microsoft Corporation | Method for managing client services across browser pages |
US7050079B1 (en) * | 2000-01-04 | 2006-05-23 | International Business Machines Corporation | System and method for dynamically generating viewable graphics |
US8296792B2 (en) * | 2000-04-24 | 2012-10-23 | Tvworks, Llc | Method and system to provide interactivity using an interactive channel bug |
US7702995B2 (en) * | 2000-04-24 | 2010-04-20 | TVWorks, LLC. | Method and system for transforming content for execution on multiple platforms |
US9788058B2 (en) | 2000-04-24 | 2017-10-10 | Comcast Cable Communications Management, Llc | Method and system for automatic insertion of interactive TV triggers into a broadcast data stream |
US20020010928A1 (en) * | 2000-04-24 | 2002-01-24 | Ranjit Sahota | Method and system for integrating internet advertising with television commercials |
US8936101B2 (en) | 2008-07-17 | 2015-01-20 | Halliburton Energy Services, Inc. | Interventionless set packer and setting method for same |
US6781609B1 (en) * | 2000-05-09 | 2004-08-24 | International Business Machines Corporation | Technique for flexible inclusion of information items and various media types in a user interface |
AU2001270222A1 (en) * | 2000-06-27 | 2002-01-08 | Ubs Ag | Method and system for providing distributed functionality and data analysis system utilizing same |
US6704776B1 (en) * | 2000-06-30 | 2004-03-09 | Webtv Networks, Inc. | Selecting attribute based content for server applications |
US6681298B1 (en) * | 2000-07-12 | 2004-01-20 | Powertv, Inc. | Hypertext markup language cache system and method |
US7739308B2 (en) | 2000-09-08 | 2010-06-15 | Oracle International Corporation | Techniques for automatically provisioning a database over a wide area network |
US7249197B1 (en) * | 2000-10-20 | 2007-07-24 | Nortel Networks Limited | System, apparatus and method for personalising web content |
US7225219B2 (en) * | 2000-11-29 | 2007-05-29 | Broadspider Networks, Inc. | Distributed caching architecture for computer networks |
US20020103974A1 (en) * | 2000-11-29 | 2002-08-01 | Giacomini Peter Joseph | Method and apparatus for economical cache population |
US9600842B2 (en) * | 2001-01-24 | 2017-03-21 | E-Numerate Solutions, Inc. | RDX enhancement of system and method for implementing reusable data markup language (RDL) |
US20020138331A1 (en) * | 2001-02-05 | 2002-09-26 | Hosea Devin F. | Method and system for web page personalization |
US20030004998A1 (en) * | 2001-06-29 | 2003-01-02 | Chutney Technologies, Inc. | Proxy-based acceleration of dynamically generated content |
US7092997B1 (en) * | 2001-08-06 | 2006-08-15 | Digital River, Inc. | Template identification with differential caching |
US7587515B2 (en) * | 2001-12-19 | 2009-09-08 | International Business Machines Corporation | Method and system for restrictive caching of user-specific fragments limited to a fragment cache closest to a user |
US7412535B2 (en) * | 2001-12-19 | 2008-08-12 | International Business Machines Corporation | Method and system for caching fragments while avoiding parsing of pages that do not contain fragments |
US7114160B2 (en) * | 2002-04-17 | 2006-09-26 | Sbc Technology Resources, Inc. | Web content customization via adaptation Web services |
US20030217076A1 (en) * | 2002-05-15 | 2003-11-20 | Heptinstall Christian Elliot | System and method for rapid generation of one or more autonomous websites |
GB0211897D0 (en) * | 2002-05-23 | 2002-07-03 | Koninkl Philips Electronics Nv | Dynamic markup language |
US20050050456A1 (en) * | 2003-08-29 | 2005-03-03 | Dehamer Brian James | Method and apparatus for supporting XML-based service consumption in a web presentation architecture |
US20050091336A1 (en) * | 2003-10-01 | 2005-04-28 | Dehamer Brian J. | Method and apparatus for supporting cookie management in a web presentation architecture |
US20050076294A1 (en) * | 2003-10-01 | 2005-04-07 | Dehamer Brian James | Method and apparatus for supporting layout management in a web presentation architecture |
US20050076329A1 (en) * | 2003-10-01 | 2005-04-07 | Christina Hsu | Method and apparatus for supporting configuration of a web application in a web presentation architecture |
US20050076291A1 (en) * | 2003-10-01 | 2005-04-07 | Yee Sunny K. | Method and apparatus for supporting page localization management in a Web presentation architecture |
US20050086292A1 (en) * | 2003-10-01 | 2005-04-21 | Yee Sunny K. | Method and apparatus for supporting preprocessing in a Web presentation architecture |
US20050086664A1 (en) * | 2003-10-01 | 2005-04-21 | Sundaresan Sankar R. | Method and apparatus for transaction tracking in a web presentation architecture |
US7146544B2 (en) * | 2003-10-01 | 2006-12-05 | Hewlett-Packard Development Company, L.P. | Method and apparatus for supporting error handling in a web presentation architecture |
US20050268248A1 (en) * | 2004-05-25 | 2005-12-01 | Microsoft Corporation | Content customization with resizability and context-sensitivity |
US7836127B2 (en) * | 2005-04-14 | 2010-11-16 | Accenture Global Services Limited | Dynamically triggering notifications to human participants in an integrated content production process |
US20070005386A1 (en) * | 2005-04-14 | 2007-01-04 | Accenture Global Services, Gmbh | Content production maintenance tool for human and non-human activity tracking |
US7984058B2 (en) * | 2005-06-02 | 2011-07-19 | Genius.Com Incorporated | Database query construction and handling |
US7734722B2 (en) * | 2005-06-02 | 2010-06-08 | Genius.Com Incorporated | Deep clickflow tracking |
US8103690B2 (en) * | 2005-06-03 | 2012-01-24 | Genius.Com | Realtime database architecture |
US7937369B1 (en) * | 2005-09-30 | 2011-05-03 | Emc Corporation | Data mover discovery of object extent |
US7685367B2 (en) * | 2006-03-08 | 2010-03-23 | Microsoft Corporation | Multi-cache cooperation for response output caching |
US9065793B2 (en) * | 2011-02-24 | 2015-06-23 | Cbs Interactive Inc. | Rendering web content using pre-caching |
US8935719B2 (en) | 2011-08-25 | 2015-01-13 | Comcast Cable Communications, Llc | Application triggering |
US9414114B2 (en) | 2013-03-13 | 2016-08-09 | Comcast Cable Holdings, Llc | Selective interactivity |
US11076205B2 (en) | 2014-03-07 | 2021-07-27 | Comcast Cable Communications, Llc | Retrieving supplemental content |
US11070608B2 (en) * | 2015-06-17 | 2021-07-20 | Fastly, Inc. | Expedited sub-resource loading |
CN105608225B (en) * | 2016-01-20 | 2019-08-30 | 北京京东尚科信息技术有限公司 | Webpage autoplacement method and device |
CN107038017B (en) * | 2016-02-03 | 2019-06-14 | 博雅网络游戏开发(深圳)有限公司 | The method and apparatus that rendering data obtains |
US10282172B2 (en) * | 2016-09-12 | 2019-05-07 | Adobe Inc. | Authoring and deploying television apps and pages in a content management system |
US11438442B1 (en) * | 2021-03-18 | 2022-09-06 | Verizon Patent And Licensing Inc. | Systems and methods for optimizing provision of high latency content by a network |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE69531599T2 (en) | 1994-12-20 | 2004-06-24 | Sun Microsystems, Inc., Mountain View | Method and device for finding and obtaining personalized information |
US5740430A (en) * | 1995-11-06 | 1998-04-14 | C/Net, Inc. | Method and apparatus for server-independent caching of dynamically-generated customized pages |
US5913033A (en) * | 1996-12-20 | 1999-06-15 | International Business Machines Corporation | Apparatus and method for retrieving information using standard objects |
US5924116A (en) * | 1997-04-02 | 1999-07-13 | International Business Machines Corporation | Collaborative caching of a requested object by a lower level node as a function of the caching status of the object at a higher level node |
US5933849A (en) * | 1997-04-10 | 1999-08-03 | At&T Corp | Scalable distributed caching system and method |
US5983227A (en) * | 1997-06-12 | 1999-11-09 | Yahoo, Inc. | Dynamic page generator |
US6192382B1 (en) * | 1997-09-24 | 2001-02-20 | Mediaone Group, Inc. | Method and system for web site construction using HTML fragment caching |
EP0905043A1 (en) * | 1997-09-27 | 1999-03-31 | The Procter & Gamble Company | Sachet with increased content quantity and process for producing the same |
US6278449B1 (en) | 1998-09-03 | 2001-08-21 | Sony Corporation | Apparatus and method for designating information to be retrieved over a computer network |
-
1998
- 1998-12-03 US US09/205,127 patent/US6345292B1/en not_active Expired - Lifetime
Cited By (52)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100121983A1 (en) * | 1999-05-25 | 2010-05-13 | Realnetworks, Inc. | System and method for providing update information |
US9350950B2 (en) * | 1999-05-25 | 2016-05-24 | Intel Corporation | System and method for providing update information |
US9633112B2 (en) | 2000-03-31 | 2017-04-25 | Kapow Software | Method of retrieving attributes from at least two data sources |
US20020152197A1 (en) * | 2001-03-01 | 2002-10-17 | Stocker Jeffrey A. | Automatic generation of personal homepages for a sales force |
US7739590B2 (en) * | 2001-03-01 | 2010-06-15 | Accenture Llp | Automatic generation of personal homepages for a sales force |
US20020188694A1 (en) * | 2001-06-07 | 2002-12-12 | Allen Yu | Cached enabled implicit personalization system and method |
US20030014439A1 (en) * | 2001-06-20 | 2003-01-16 | International Business Machines Corporation | Defining a markup language representation for state chart data |
US20030188021A1 (en) * | 2001-12-19 | 2003-10-02 | International Business Machines Corporation | Method and system for processing multiple fragment requests in a single message |
US8032586B2 (en) | 2001-12-19 | 2011-10-04 | International Business Machines Corporation | Method and system for caching message fragments using an expansion attribute in a fragment link tag |
US7426534B2 (en) | 2001-12-19 | 2008-09-16 | International Business Machines Corporation | Method and system for caching message fragments using an expansion attribute in a fragment link tag |
US20080005273A1 (en) * | 2001-12-19 | 2008-01-03 | Agarwalla Rajesh S | Method and system for caching role-specific fragments |
US7509393B2 (en) * | 2001-12-19 | 2009-03-24 | International Business Machines Corporation | Method and system for caching role-specific fragments |
US20030187935A1 (en) * | 2001-12-19 | 2003-10-02 | International Business Machines Corporation | Method and system for fragment linking and fragment caching |
US7987239B2 (en) | 2001-12-19 | 2011-07-26 | International Business Machines Corporation | Method and system for caching role-specific fragments |
US20030191812A1 (en) * | 2001-12-19 | 2003-10-09 | International Business Machines Corporation | Method and system for caching role-specific fragments |
US7730154B2 (en) | 2001-12-19 | 2010-06-01 | International Business Machines Corporation | Method and system for fragment linking and fragment caching |
US7171470B2 (en) | 2003-02-20 | 2007-01-30 | International Business Machines Corporation | Grid service scheduling of related services using heuristics |
US20090055727A1 (en) * | 2005-11-18 | 2009-02-26 | Kapow Technologies A/S | Method of performing web-clipping, a web-clipping server and a system for web-clipping |
US20090265420A1 (en) * | 2006-05-15 | 2009-10-22 | Kapow Technologies R & D A/S | Method of rendering at least one element in a client browser |
US20080134083A1 (en) * | 2006-11-30 | 2008-06-05 | Microsoft Corporation | Rendering document views with supplemental information content |
US8185826B2 (en) | 2006-11-30 | 2012-05-22 | Microsoft Corporation | Rendering document views with supplemental information content |
US9122650B1 (en) | 2007-11-14 | 2015-09-01 | Appcelerator, Inc. | Web server based on the same paradigms as web clients |
US8914774B1 (en) | 2007-11-15 | 2014-12-16 | Appcelerator, Inc. | System and method for tagging code to determine where the code runs |
US8954989B1 (en) | 2007-11-19 | 2015-02-10 | Appcelerator, Inc. | Flexible, event-driven JavaScript server architecture |
US8260845B1 (en) | 2007-11-21 | 2012-09-04 | Appcelerator, Inc. | System and method for auto-generating JavaScript proxies and meta-proxies |
US8266202B1 (en) | 2007-11-21 | 2012-09-11 | Appcelerator, Inc. | System and method for auto-generating JavaScript proxies and meta-proxies |
US8510378B2 (en) | 2007-11-21 | 2013-08-13 | Appcelerator, Inc. | System and method for auto-generating JavaScript |
US8719451B1 (en) | 2007-11-23 | 2014-05-06 | Appcelerator, Inc. | System and method for on-the-fly, post-processing document object model manipulation |
US8566807B1 (en) | 2007-11-23 | 2013-10-22 | Appcelerator, Inc. | System and method for accessibility of document object model and JavaScript by other platforms |
US8819539B1 (en) | 2007-12-03 | 2014-08-26 | Appcelerator, Inc. | On-the-fly rewriting of uniform resource locators in a web-page |
US8806431B1 (en) | 2007-12-03 | 2014-08-12 | Appecelerator, Inc. | Aspect oriented programming |
US8756579B1 (en) | 2007-12-03 | 2014-06-17 | Appcelerator, Inc. | Client-side and server-side unified validation |
US8527860B1 (en) | 2007-12-04 | 2013-09-03 | Appcelerator, Inc. | System and method for exposing the dynamic web server-side |
US8938491B1 (en) | 2007-12-04 | 2015-01-20 | Appcelerator, Inc. | System and method for secure binding of client calls and server functions |
US8639743B1 (en) | 2007-12-05 | 2014-01-28 | Appcelerator, Inc. | System and method for on-the-fly rewriting of JavaScript |
US8335982B1 (en) | 2007-12-05 | 2012-12-18 | Appcelerator, Inc. | System and method for binding a document object model through JavaScript callbacks |
US8285813B1 (en) | 2007-12-05 | 2012-10-09 | Appcelerator, Inc. | System and method for emulating different user agents on a server |
US9148467B1 (en) | 2007-12-05 | 2015-09-29 | Appcelerator, Inc. | System and method for emulating different user agents on a server |
US20090254867A1 (en) * | 2008-04-03 | 2009-10-08 | Microsoft Corporation | Zoom for annotatable margins |
US8291079B1 (en) | 2008-06-04 | 2012-10-16 | Appcelerator, Inc. | System and method for developing, deploying, managing and monitoring a web application in a single environment |
US20090307618A1 (en) * | 2008-06-05 | 2009-12-10 | Microsoft Corporation | Annotate at multiple levels |
US8880678B1 (en) | 2008-06-05 | 2014-11-04 | Appcelerator, Inc. | System and method for managing and monitoring a web application using multiple cloud providers |
US8954553B1 (en) | 2008-11-04 | 2015-02-10 | Appcelerator, Inc. | System and method for developing, deploying, managing and monitoring a web application in a single environment |
US9195638B2 (en) | 2010-07-12 | 2015-11-24 | Alibaba Group Holding Limited | Method and apparatus of processing nested fragment caching of a web page |
US8892684B2 (en) | 2012-05-25 | 2014-11-18 | Microsoft Corporation | Dynamic selection of resources for compression in a content delivery network |
US9282137B2 (en) | 2012-05-25 | 2016-03-08 | Microsoft Technology Licensing, Llc | Dynamic package creation for predictive page load optimization |
US9160803B2 (en) * | 2012-06-21 | 2015-10-13 | International Business Machines Corporation | Web storage optimization |
US9160804B2 (en) * | 2012-06-21 | 2015-10-13 | International Business Machines Corporation | Web storage optimization |
US20130346474A1 (en) * | 2012-06-21 | 2013-12-26 | International Business Machines Corporation | Web storage optimization |
US20130346536A1 (en) * | 2012-06-21 | 2013-12-26 | International Business Machines Corporation | Web storage optimization |
US9781135B2 (en) | 2014-06-20 | 2017-10-03 | Microsoft Technology Licensing, Llc | Intelligent web page content blocking |
US10200386B2 (en) | 2014-06-20 | 2019-02-05 | Microsoft Technology Licensing, Llc | Intelligent web page content blocking |
Also Published As
Publication number | Publication date |
---|---|
US6345292B1 (en) | 2002-02-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6345292B1 (en) | Web page rendering architecture | |
US6564251B2 (en) | Scalable computing system for presenting customized aggregation of information | |
US7194506B1 (en) | Method and system for cache management of locale-sensitive content | |
US9703885B2 (en) | Systems and methods for managing content variations in content delivery cache | |
US7509404B2 (en) | Methods and systems for partial page caching of dynamically generated content | |
US6021426A (en) | Method and apparatus for dynamic data transfer on a web page | |
US6714926B1 (en) | Use of browser cookies to store structured data | |
US6192382B1 (en) | Method and system for web site construction using HTML fragment caching | |
US20030004998A1 (en) | Proxy-based acceleration of dynamically generated content | |
US7155489B1 (en) | Acquiring web page information without commitment to downloading the web page | |
USRE39184E1 (en) | Identifying, processing and caching object fragments in a web environment | |
US9836445B2 (en) | Dynamic page generator | |
US8972998B2 (en) | Processing annotation requests using multithreaded constituent task and independent input/output tasks | |
US7657595B2 (en) | Method and system for generating auxiliary-server cache identifiers | |
KR101013046B1 (en) | Methods, systems, and computer program products for client side prefetching and caching of portlets | |
US9111003B2 (en) | Scalable derivative services | |
US20020194382A1 (en) | Method and system for efficient and automated version management of embedded objects in web documents | |
US20060129657A1 (en) | Method and system for file-system based caching | |
US20020078087A1 (en) | Content indicator for accelerated detection of a changed web page | |
EP1461928A1 (en) | Method and system for network caching | |
CN1339747A (en) | System and method for high speed buffer storage file information | |
Signer et al. | A personal assistant for Web database caching | |
Gordon et al. | Bluejay: a browser for linear units in Java | |
Buford | A Transfer Protocol for an Open Hyperdocument Model Server |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DAUGHERTY, BRIAN R.;BECK, MARC T.;CLORE, DONALD J.;REEL/FRAME:009743/0984;SIGNING DATES FROM 19990112 TO 19990120 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
CC | Certificate of correction | ||
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
FPAY | Fee payment |
Year of fee payment: 12 |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034541/0001 Effective date: 20141014 |