WO2000031628A1 - Dynamic data cache for object-oriented computing environments - Google Patents

Dynamic data cache for object-oriented computing environments Download PDF

Info

Publication number
WO2000031628A1
WO2000031628A1 PCT/US1999/024357 US9924357W WO0031628A1 WO 2000031628 A1 WO2000031628 A1 WO 2000031628A1 US 9924357 W US9924357 W US 9924357W WO 0031628 A1 WO0031628 A1 WO 0031628A1
Authority
WO
Grant status
Application
Patent type
Prior art keywords
object
data
property
cache
access
Prior art date
Application number
PCT/US1999/024357
Other languages
French (fr)
Inventor
David A. Sobeski
Felix G. T. I. Andrew
Original Assignee
Microsoft Corporation
Priority date (The priority date 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 date listed.)
Filing date
Publication date

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/448Execution paradigms, e.g. implementations of programming paradigms
    • G06F9/4488Object-oriented

Abstract

Dynamic data caching for object-oriented environments. In one embodiment, a system having a container and external objects, the container having a data object, a data cache object, internal objects and a controller object. The data object has static properties. The data cache object provides for access to the data object, and temporarily stores dynamic properties for the data object. The controller object provides for access to the data cache object.

Description

DYNAMIC DATA CACHE FOR OBJECT-ORIENTED COMPUTING ENVIRONMENTS

RELATED APPLICATIONS

This application is related to the following applications, which are hereby incorporated by reference: [SLWK docket 777.169US1], [SLWK docket 777.172US1].

FIELD OF THE INVENTION

This invention relates generally to object-oriented computing environments, and more particularly to a dynamic data cache for such environments.

BACKGROUND OF THE INVENTION

Object-oriented programming environments are currently the standard environment in which computer programs are developed. For example, within the Microsoft Windows operating system, programs may be developed using the Component Object Model (COM) architecture. Object-oriented programming environments provide a modular manner by which developers can develop complex and sophisticated computer programs.

Generally, an object may include data and methods by which that data is accessed and changed. Thus, new methods may be added to the object for accessing and changing the data in other ways not previously possible, without affecting existing methods, and the external objects that rely on these existing methods. Upon receiving a message, or in response to an event, an object typically executes a particular method, resulting in the data within that object being retrieved or changed. SUMMARY OF THE INVENTION

The invention provides for dynamic data cache for object-oriented environments. In one embodiment, a system includes at a container and at least one external object. The container includes a data object, a data cache object, at least one internal object, and a controller object. The container may also be termed a control (as opposed to a controler), or a form. The data object has at least one static property. The data cache object provides for access to the data object, and also is able to temporarily store at least one dynamic property for the data object. The controller object provides for access to the data cache object, via messages and/or events. Both the internal and external objects are able to access both the static and dynamic properties of the data object (via the controller object communicating with the data cache object). Thus, in one embodiment of the invention, the dynamic data cache is dynamic in that it is able to store dynamic properties for the data object. The dynamic data cache in one embodiment is dynamic in another sense: storing changes of the state of the properties of the object, which are not committed to the data itself until desired. Thus, the dynamic nature of the dynamic data cache in this sense relates to the fact that the state of the properties of the object can change over time, such that these state changes are maintained by the cache, and not committed back to the data itself until the cache is so instructed. Therefore, the dynamic data cache is dynamic in nature in two different manners, in one embodiment of the invention.

The dynamic data caching of the invention provides for advantages not found in the prior art. For example, internal and external objects of the container are able to create and access new (temporary) dynamic properties of the data object, which are accommodated by the data cache object. This is accomplished by these objects communicating with the controller object, which itself communicates with the data cache object. Thus, the dynamic data cache object provides both internal and external access to the static and dynamic properties of the data object, where external and internal objects communicate with the dynamic data cache object through the controller object). 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.

BRIEF DESCRIPTION OF THE DRAWINGS

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(a) shows a diagram of a screen shot of a box in accordance with an embodiment of the invention;

FIG. 3(b) shows a diagram of a screen shot of another box in accordance with an embodiment of the invention;

FIG. 4(a) shows a flowchart illustrating a method according to one embodiment of the invention; and,

FIG. 4(b) shows a flowchart illustrating another method according to one embodiment of the invention.

DETAILED DESCRIPTION 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, methods, in accordance with embodiments of the invention, are provided. Finally, in the fourth section, a conclusion of the detailed description is provided.

Hardware and Operating Environment Referring to FIG. 1, a diagram of the hardware and operating environment in conjunction with which embodiments of the mvention 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 PCS, 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 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. 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. 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. 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 (not shown) 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. 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 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. 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 the local network 51 through a network interface or adapter 53, which is one type of communications device. 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. In a networked environment, program modules depicted relative to the personal 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.

System In this section of the detailed description, a description of a computerized system according to an embodiment of the invention is provided. The description is provided by reference to FIG. 2. Referring now to FIG. 2, a system according to an embodiment of the invention is shown. The system includes a container object 200 (also referred to as a control, as opposed to a controller), and one or more external objects 202. The container object 202 includes a data object 204, a data cache object 206, a controller object 208, and one or more internal objects 210. Each of these objects can in one embodiment be a Component Object Model (COM) object, for use in programming in conjunction with the Microsoft Windows operating system, although the invention is not so limited.

Data object 204 is the object that stores the data of the container object 200. In one embodiment, such data is stored as properties. The object 204 stores static properties, which are data that is always associated with the object 204 (as opposed to dynamic properties, as will be described). The data cache object 206 is communicatively coupled to the data object 204 and the controller object 208. The data cache object 206 thus is the only manner through which access is able to be made to the data stored in the data object 204. That is, the data cache object 206 is such that all access to the static properties of the object 204 is made through object 206.

In addition, the data cache object 206 temporally stores any dynamic properties for the data object 204 that may have been requested to be added to the data object 204 by other (internal or external) objects. Dynamic properties are data that is not permanently associated with the definition of data object 204, as opposed to static properties that always are. Thus, the data cache object 206 is a mechanism that allows another object to store state and other information, in the form of dynamic properties, that may be of interested to itself and other objects. For example, an object may add a text color property to an object that does not currently have this data. When another objects asks for the properties of this object, it then is able to see that the text color property exists, and to use this information. It is noted that in one embodiment of the invention, external or internal object access to the properties of the object (via the controller object, which itself communicates with the dynamic cache object) is such that the object accessing the property does not itself know - or care - whether the property being accessed is dynamic or static.

The data cache object 206 also acts as a cache for the data object 204. In such an embodiment, the object 206 can have two modes. In a cache mode, all the changes requested by other objects to the data within object 204 are cached in object 206, such that the changes are not made to the permanent data in object 204 until one of these other objects commits its data changes. Furthermore, in a pass-through mode, all the changes requested by other objects to the data within object 204 are immediately passed through to object 206, such that changes are immediately made to the data stored in object 204. This is the default mode in one embodiment of the invention. In other words, the data cache object 206 maintains what is known in the art as a dirty state. Thus, if a method asks to change the value of data to the already existing value, the data cache object 206 ignores the change. However, if the old value and the new value are different, then the data is marked as dirty - - that is, the value stored by object 206 is different than that stored by object 204, and remains that way until the data is committed back to object 204. Controller object 208 is communicatively coupled to the data cache object 206, the external objects 202, and the internal objects 210. The controller object 208 is the object through which all accesses to the data cache object 206 are made. In one embodiment, such accesses can be by messages sent by other objects, or events that have been preset by objects and that have been triggered. It is noted that the controller object 208 communicates indirectly to the data object 204 through the data cache object 206. Furthermore, other objects, such as external objects 202 and internal objects 210, communicate indirectly to the data cache object 206 through the controller object 208.

The internal objects 210 are part of the container object 200, and are able to access both the static properties of the data object 204 (via the controller object, which is coupled to the data cache object 206), as well as the dynamic properties of the data object 204, as maintained and accommodated by the data cache object 206 (again, via the controller object, which is coupled to the data cache object 206). They are communicatively coupled to the controller object 208. The internal objects 210 can add new (dynamic) properties to the data object 204 by making a request of the controller object 208, which relays the message to the data cache object 206, as well as access dynamic or static properties, again by making an appropriate request to the controller object 208. The external objects 202 are defined primarily as being external to the container object 200. The objects 202 are communicatively coupled to the container object 200 via the controller object 208. Like the internal objects 210, they are able to access the static and dynamic properties of the object via an appropriate request to the controller object 208 of the container object 200. Thus, the external objects 202 are able to access the static and dynamic properties of the object by making a request to the controller object 208, which itself communicates with the data cache object 206. The architecture and system described in conjunction with FIG. 2 can be used to formulate many different types of container objects. The invention is not particularly limited. However, two illustrative examples are shown by reference to FIG. 3(a) and FIG. 3(b), which are screen shots of boxes that may be a result of different container objects, according to varying embodiments of the invention.

Referring first to FIG. 3(a), box 300 is a select file dialog box, that includes a file selection area 302, option check boxes 304 and 306, an OK button 308, and a cancel button 310. Examples of such dialog boxes are known within the art. Thus, a user moves the pointer 312 to select the desired file shown in file area 302 (including using the scrolling buttons or bar if desired), checks the desired options via check boxes 304 and 306, and then clicks on the OK button 308 to relay these selections. Alternatively, the user has the option of clicking the cancel button 310 to cancel the operation. Thus, a container object for such an embodiment of the invention may encompass the entire dialog box. Internal objects for such a container may include the individual internal objects for each of the file area 302, each of the option check boxes 304 and 306, as well as the OK button 308 and the cancel button 310. Assuming that the data cache object of such an object is operating in cache mode, the user is able to make selections within the file area 302, click and/or unclick the option check boxes 304 and 306, etc., all of which cause the data within the data cache object to change.

However, the data in the data object does not change until the user clicks on the OK cancel button 308, which causes the internal object associated with this button to commit the changes made to the cache object to the data object. Conversely, if the user clicks on the cancel button 310, then the internal object associated therewith instructs the cache object not to commit any changes that have been made. The internal objects in the embodiment of FIG. 3(a) can be referred to as displayer objects, or displayers, in that the cause the display of information. Referring next to FIG. 3(b), box 350 is a save file dialog box, that includes a file name entry area 352, a save button 354, and a cancel button 356. Examples of such dialog boxes are known within the art. Thus, a user, after entering in the desired file name in area 352, moves the pointer 358 over save button 354, and clicks to register the entered file name — that is, to commit the file name that has been entered in the data cache object of this container object to the data object.

In particular, however, when the pointer 358 is moved over the save button 354, a tool tip banner 360 is displayed, to indicate to the user particular instructions as to the save button 354. In such an instance, the internal object related to the save button 354 may have previously created a tracking dynamic property to the container object (viz., to the data object thereof), which is in actuality maintained by the data cache object. Once this dynamic property has been added directly to the data cache object, the internal object related to the save button 354 is able to change the data of the property — i.e., the text of the tool tip banner 360 (click to save file, as shown in FIG. 3(b)).

Thus, dynamic properties such as this tracking dynamic property may be added to the data object, without interfering with the manner by which other objects interface with the data object. This is because the data cache object in actuality stores the data regarding the added dynamic property. Once any changes made to the container object are committed, the dynamic property information is lost; that is, unlike static property information, it is not saved in the data object of the container object.

It is noted that as to the embodiments of the invention described in conjunction with FIG. 2 and FIGs. 3(a) and 3(b), the objects can in one embodiment be stored on a computer-readable storage medium, such as a floppy disk or a compact-disc read-only-memory (CD-ROM). In another embodiment, the objects as data representing them and residing in a memory of a computer, executed by the processor thereof. The invention is not particularly limited, however. Methods 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(a) and 4(b). 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 first to FIG. 4(a), a flowchart of a method according to one embodiment of the invention is shown. The method of FIG. 4(a) illustrates the manner by which a dynamic data cache (such as the cache object described in the previous section) operates, according to one embodiment. In 400, the cache defaults to a pass-through mode, in which data changes made to static properties automatically pass through the cache to immediately change the data stored in a data object with which the cache is associated. In 402, the cache receives a switch command, to switch the cache from pass-through mode to cache mode. This change is made in 404. Upon entering pass-through mode, the cache copies the initial values of the static properties stored in the data object into the cache in 406. In another embodiment of the invention, no copies are made. All unmodified static properties are obtained from the data object. Otherwise, the value in the cache is used. When a change is made to a property in this embodiment, it is stored in the cache.

Thereafter, changes requested to be made of the data of the static properties of the data within the data object are in actuality made only to the data stored in the cache. In 408, the cache waits for a command. If it is some type of change data command, then control proceeds to 410, where the data is changed as requested, but only to the data as stored in the cache, not in the actual data object. If the command is a commit data command, then the cache commits the changed data to the data object in 412, by copying the data as changed in the cache to the data object, overwriting the original values in the data object. Finally, in 414, if the command is a do not commit data command (i.e., a cancel or discard command), then the changed data in the cache is not copied to the original data object.

Referring next to FIG. 4(b), a flowchart of another method according to one embodiment of the invention is shown. The method of FIG. 4(b) may be performed in one embodiment after or before (that is, in conjunction with) the method of FIG. 4(a)). The method of FIG. 4(b) illustrates the manner by which a dynamic data cache (such as the cache object described in the previous section) receives a dynamic (new) property. In 450, a command to create a new dynamic property for a data object is received by the cache. In 452, the cache determines if the new dynamic property already exists. If it does, then control proceeds to 456.

If the property does not already exist, however, then in 454, the cache creates the new property. Note that data change commands regarding the dynamic property are made in the cache itself; the data object, in other words, does not actually store the data regarding the dynamic property. In 456, the cache waits to receive a clear command, such that in 458, the cache clears the dynamic property and the data regarding the property from its memory.

Conclusion

Dynamic data caching 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

We claim:
1. A system comprising: a container comprising: a data object having at least one static property; a data cache object through which all access to the at least one static property of the data object is made and to temporarily store at least one dynamic property for the data object; a controller object through which all access to the data cache object is made via at least one of messages and events at least one internal object to access the at least one static property and the at least one dynamic property; and, at least one external object to access the at least one static property and the at least one dynamic property.
2. The system of claim 1 , wherein the data cache obj ect has a cache mode in which all changes made to the at least one static property are cached until committed to the data object.
3. The system of claim 2, wherein the data cache obj ect further has a pass- through mode in which all changes made to the at least one static property are automatically reflected back to the data object.
4. The system of claim 3, wherein the data cache object defaults to the pass- through mode.
5. A container comprising: a data object having at least one static property; a data cache object through which all access to the at least one static property of the data object is made and to temporarily store at least one dynamic property for the data object; and, a controller object through which all access to the data cache object is made via at least one of messages and events.
6. The container of claim 5, further comprising at least one internal object to access the at least one static property and the at least one dynamic property.
7. The container of claim 5, wherein the data cache object has a cache mode in which all changes made to the at least one static property are cached until committed to the data object.
8. The container of claim 7, wherein the data cache object further has a pass-through mode in which all changes made to the at least one static property are automatically reflected back to the data object.
9. The container of claim 8, wherein the data cache object defaults to the pass-through mode.
10. A method comprising: receiving a command to create a new property for a data object; and, upon receiving the command to create the new property, creating the new property within a data cache object such that data regarding the new property is accessible to and changeable by only internal objects.
11. The method of claim 10, further comprising: copying data from a data object to a data cache object; receiving a command; upon the command comprising a change data command, changing the data in the data cache object; and, upon the command comprising a commit data command, copying the data from the data cache object to the data object.
12. The method of claim 11, further initially comprising: defaulting to a pass-through mode in which a received command comprising a change data command results in changing the data in the data object; and, upon receiving a command comprising a switch command, changing to a cache mode.
13. A computer comprising: a processor; a memory; and, data residing in the memory for execution by the processor and representing: a container comprising a data object having at least one static property; a data cache object through which all access to the at least one static property of the data object is made and to temporarily store at least one dynamic property for the data object; and, a controller object through which all access to the data cache object is made via at least one of messages and events; and, at least one external object to access the at least one static property and the at least one dynamic property.
14. A computer-readable storage medium having stored thereon data representing: a container comprising: a data object having at least one static property; a data cache object through which all access to the at least one static property of the data object is made and to temporarily store at least one dynamic property for the data object; and, a controller object through which all access to the data cache object is made via at least one of messages and events; and, at least one external object to access the at least one static property and the at least one dynamic property.
PCT/US1999/024357 1998-11-25 1999-10-19 Dynamic data cache for object-oriented computing environments WO2000031628A1 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
US20048998 true 1998-11-25 1998-11-25
US09199604 US6795968B1 (en) 1998-11-25 1998-11-25 Dynamic object behavior for object-oriented-computing environments
US09200674 US6304879B1 (en) 1998-11-25 1998-11-25 Dynamic data cache for object-oriented computing environments
US09/200,674 1998-11-25
US09/200,489 1998-11-25
US09/199,604 1998-11-25

Publications (1)

Publication Number Publication Date
WO2000031628A1 true true WO2000031628A1 (en) 2000-06-02

Family

ID=27394043

Family Applications (3)

Application Number Title Priority Date Filing Date
PCT/US1999/024343 WO2000031627A1 (en) 1998-11-25 1999-10-19 Dynamic object behavior for object-oriented computing environments
PCT/US1999/024358 WO2000031629A1 (en) 1998-11-25 1999-10-19 Object model for object-oriented computing environments
PCT/US1999/024357 WO2000031628A1 (en) 1998-11-25 1999-10-19 Dynamic data cache for object-oriented computing environments

Family Applications Before (2)

Application Number Title Priority Date Filing Date
PCT/US1999/024343 WO2000031627A1 (en) 1998-11-25 1999-10-19 Dynamic object behavior for object-oriented computing environments
PCT/US1999/024358 WO2000031629A1 (en) 1998-11-25 1999-10-19 Object model for object-oriented computing environments

Country Status (1)

Country Link
WO (3) WO2000031627A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7680875B1 (en) 2002-04-01 2010-03-16 Novell, Inc. Markers for cached objects

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0757313A1 (en) * 1995-08-01 1997-02-05 Intergraph Corporation System for adding attributes to an object at run time in an object oriented computer environment
US5608909A (en) * 1994-04-15 1997-03-04 Microsoft Corporation Method and system for caching presentation data of a source object in a presentation cache
US5692187A (en) * 1995-02-14 1997-11-25 General Magic Shadow mechanism having masterblocks for a modifiable object oriented system

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6044224A (en) * 1996-06-26 2000-03-28 Sun Microsystems, Inc. Mechanism for dynamically associating a service dependent representation with objects at run time
US5892949A (en) * 1996-08-30 1999-04-06 Schlumberger Technologies, Inc. ATE test programming architecture
US5907847A (en) * 1996-09-26 1999-05-25 Sun Microsystems, Inc. Method and apparatus for coupling object state and behavior in a database management system
EP0938701B1 (en) * 1996-11-14 2003-11-05 Alcatel USA Sourcing, L.P. Generic software state machine and method of constructing dynamic objects for an application program

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5608909A (en) * 1994-04-15 1997-03-04 Microsoft Corporation Method and system for caching presentation data of a source object in a presentation cache
US5692187A (en) * 1995-02-14 1997-11-25 General Magic Shadow mechanism having masterblocks for a modifiable object oriented system
EP0757313A1 (en) * 1995-08-01 1997-02-05 Intergraph Corporation System for adding attributes to an object at run time in an object oriented computer environment

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
JAAKSI A: "IMPLEMENTING INTERACTIVE APPLICATIONS IN C++", SOFTWARE PRACTICE & EXPERIENCE,GB,JOHN WILEY & SONS LTD. CHICHESTER, vol. 25, no. 3, 1 March 1995 (1995-03-01), pages 271 - 289, XP000655503, ISSN: 0038-0644 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7680875B1 (en) 2002-04-01 2010-03-16 Novell, Inc. Markers for cached objects

Also Published As

Publication number Publication date Type
WO2000031629A1 (en) 2000-06-02 application
WO2000031627A1 (en) 2000-06-02 application

Similar Documents

Publication Publication Date Title
US6249817B1 (en) Data-update monitoring in communications network
US4868763A (en) Knowledge-based system having plural processors
US5751958A (en) Allowing inconsistency in a distributed client-server application
US5956486A (en) Method and apparatus for monitoring multiple electronic mail systems
US6842779B1 (en) Agent accessory tool cooperating with integrated application on WEB server by HTTP protocol
US5625820A (en) System managed logging of objects to speed recovery processing
US6256637B1 (en) Transactional virtual machine architecture
US6708173B1 (en) Method and apparatus for multiple application trace streams
US5689637A (en) Console simulator, multi-console management system and console management distribution system
US7467137B1 (en) System and method for information retrieval employing a preloading procedure
US7739282B1 (en) Method and system for tracking client software use
US7103594B1 (en) System and method for information retrieval employing a preloading procedure
US7337210B2 (en) Method and apparatus for determining availability of a user of an instant messaging application
US5829001A (en) Database updates over a network
US6772107B1 (en) System and method for simulating activity on a computer network
US5504895A (en) Method of managing data structure containing both persistent data and transient data
Vogels File system usage in Windows NT 4.0
US5023851A (en) Method for presenting electronic calendar information in an interactive information handling system
US7617458B1 (en) Managing navigation and history information
US5950216A (en) Method and system for marking and subsequently retrieving a collection of objects within a multipage compound document utilizing selectable page numbered dialog boxes
US5211563A (en) Computer assisted learning support system and processing method therefor
US5867678A (en) Method and system for searching and retrieving specific types of objects contained within a compound document
US6924797B1 (en) Arrangement of information into linear form for display on diverse display devices
US5964834A (en) System grouping clipboard memories associating with computers in a network into a shared clipboard memory for sharing data object in the network
US5768511A (en) Method and system for managing objects in networked computer system with action performed in the server and object updated in the client

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): JP

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase