US20020091874A1 - Deferred reconstruction of objects and remote loading for event notification in a distributed system - Google Patents

Deferred reconstruction of objects and remote loading for event notification in a distributed system Download PDF

Info

Publication number
US20020091874A1
US20020091874A1 US09/891,178 US89117801A US2002091874A1 US 20020091874 A1 US20020091874 A1 US 20020091874A1 US 89117801 A US89117801 A US 89117801A US 2002091874 A1 US2002091874 A1 US 2002091874A1
Authority
US
United States
Prior art keywords
stream
machine
event
notification
module configured
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.)
Abandoned
Application number
US09/891,178
Inventor
Peter Jones
Ann Wollrath
James Waldo
Kenneth Arnold
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sun Microsystems Inc
Original Assignee
Sun Microsystems Inc
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
Priority claimed from US08/950,756 external-priority patent/US6253256B1/en
Application filed by Sun Microsystems Inc filed Critical Sun Microsystems Inc
Priority to US09/891,178 priority Critical patent/US20020091874A1/en
Publication of US20020091874A1 publication Critical patent/US20020091874A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR 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/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/542Event management; Broadcasting; Multicasting; Notifications
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR 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/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/547Remote procedure calls [RPC]; Web services
    • G06F9/548Object oriented; Remote method invocation [RMI]

Definitions

  • the present invention relates to a system and method for transmitting objects between machines in a distributed system and more particularly relates to deferred reconstruction of objects for event notification in a distributed system.
  • Distributed systems usually contain a number of different types of machines interconnected by communications networks. Each machine has its own internal data types, its own address alignment rules, and its own operating system. This heterogeneity causes problems when building distributed systems. As a result, program developers must include in programs developed for such heterogeneous distributed systems the capability of dealing with ensuring that information is handled and interpreted consistently on different machines.
  • RPC is a mechanism for providing synchronized communication between two processes (e.g., program, applet, etc.) running on the same machine or different machines.
  • one process e.g., a client program
  • sends a message to another process e.g., a server program.
  • the client program it is possible for the client program to transmit the message and then begin a new activity, or for the server program's environment to buffer the incoming message until the server program is ready to process a new message.
  • RPC however, imposes constraints on synchronism because it closely models the local procedure call, which requires passing parameters in one direction, blocking the calling process (i.e., the client program) until the called procedure of the server program is complete, and then returning a response.
  • RPC thus involves two message transfers, and the synchronization of the two processes for the duration of the call.
  • the RPC mechanism is usually implemented in two processing parts using the local procedure call paradigm, one part being on the client side and the other part being on the server side. Both of these parts will be described below with reference to FIG. 1.
  • FIG. 1 is a diagram illustrating the flow of call information using an RPC mechanism.
  • a client program 100 issues a call (step 102 ).
  • the RPC mechanism 101 then packs the call as arguments of a call packet (step 103 ), which the RPC mechanism 101 then transmits to a server program 109 (step 104 ).
  • the call packet also contains information to identify the client program 100 that first sent the call.
  • the RPC mechanism 101 enters a wait state during which it waits for a response from the server program 109 .
  • the RPC mechanism 108 for the server program 109 (which may be the same RPC mechanism as the RPC mechanism 101 when the server program 109 is on the same platform as the client program 100 ) receives the call packet (step 110 ), unpacks the arguments of the call from the call packet (step 111 ), identifies, using the call information, the server program 109 to which the call was addressed, and provides the call arguments to the server program 169 .
  • the server program receives the call (step 112 ), processes the call by invoking the appropriate procedure (step 115 ), and returns a response to the RPC mechanism 108 (step 116 ).
  • the RPC mechanism 108 then packs the response in a response packet (step 114 ) and transmits it to the client program 100 (step 113 ).
  • Receiving the response packet triggers the RPC mechanism 101 to exit the wait state and unpack the response from the response packet (step 106 ).
  • RPC 101 then provides the response to the client program 100 in response to the call (step 105 ).
  • This is the process flow of the typical RPC mechanism modeled after the local procedure call paradigm. Since the RPC mechanism uses the local procedure call paradigm, the client program 100 is blocked at the call until a response is received. Thus, the client program 100 does not continue with its own processing after sending the call; rather, it waits for a response from the server program 109 .
  • the JavaTM programming language is an object-oriented programming language that is typically compiled into a platform-independent format, using a bytecode instruction set, which can be executed on any platform supporting the Java virtual machine (JVM).
  • JVM Java virtual machine
  • This language is described, for example, in a text entitled “The Java Language Specification” by James Gosling, Bill Joy, and Guy Steele, Addison-Wesley, 1996, which is incorporated herein by reference.
  • the JVM is described, for example, in a text entitled “The Java Virtual Machine Specification,” by Tim Lindholm and Frank Yellin, Addison Wesley, 1996, which is incorporated herein by reference.
  • Java and Java-based trademarks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
  • the JVM may be implemented on any type of platform, implementing distributed programs using the JVM significantly reduces the difficulties associated with developing programs for heterogenous distributed systems.
  • the JVM uses a Java remote method invocation (RMI) system that enables communication among programs of the system.
  • RMI Java remote method invocation
  • Sun Microsystems, Inc. (1997), which is available via universal resource locator (URL) http://www.javasoft.com/products/jdk/1.1/docs/guide/rmi/spec/rmiTOC.doc.html.
  • FIG. 2 is a diagram illustrating the flow of objects in an object-oriented distributed system 200 including machines 201 and 202 for transmitting and receiving method invocations using the JVM.
  • machine 201 uses RMI 205 for responding to a call for object 203 by converting the object into a byte stream 207 including an identification of the type of object transmitted and data constituting the object. While machine 201 is responding to the call for object 203 , a process running on the same or another machine in system 200 may continue operation without waiting for a response to its request.
  • Machine 202 receives the byte stream 207 . Using RMI 206 , machine 202 automatically converts it into the corresponding object 204 , which is a copy of object 203 and which makes the object available for use by a program executing on machine 202 . Machine 202 may also transmit the object to another machine by first converting the object into a byte stream and then sending it to the third machine, which also automatically converts the byte stream into the corresponding object.
  • the automatic reconstruction of the objects from the byte stream in this manner sometimes requires unnecessary processing. For example, there are times when a call is made that does not require actual or immediate interaction with the object, both of which require conversion of the byte stream to object form. Instead, a call may require passing the object to another call or storing it for later use. In this situation, the reconstruction of the object on an intermediate machine is unnecessary, especially if the object is to be transmitted to another machine. Examples of such a situation include transmission of objects for notification of events in a distributed system.
  • a method consistent with the present invention specifies an object associated with a request for notification of a particular event within a distributed system.
  • the object is converted into a stream containing a self-describing form of the object, and the stream is provided for selective transmission to a machine where the object is reconstructed by accessing program code identified in the stream upon occurrence of the event.
  • Another method consistent with the present invention receives at a first machine a stream containing a self-describing form of an object associated with a request for notification of a particular event within a distributed system.
  • the method includes determining whether to send the stream to a second machine and selectively sending the stream to the second machine for reconstruction of the object by accessing program code identified in the stream, the first machine providing notification of the event.
  • An apparatus consistent with the present invention specifies an object associated with a request for notification of a particular event within a distributed system.
  • the apparatus converts the object into a stream containing a self-describing form of the object and provides the stream for selective transmission to a machine where the object is reconstructed by accessing program code identified in the stream upon occurrence of the event.
  • Another apparatus consistent with the present invention receives at a first machine a stream containing a self-describing form of an object associated with a request for notification of a particular event within a distributed system.
  • the apparatus determines whether to send the stream to a second machine and selectively sends the stream to the second machine for reconstruction of the object by accessing program code identified in the stream, the first machine providing notification of the event.
  • FIG. 1 is a diagram illustrating the flow of call information using an RPC mechanism
  • FIG. 2 is a diagram illustrating the transmission of objects in an object-oriented distributed system
  • FIG. 3 is a diagram of an exemplary distributed processing system that can be used in an implementation consistent with the present invention
  • FIG. 4 is a diagram of an exemplary distributed system infrastructure
  • FIG. 5 is a diagram of a computer in a distributed system infrastructure shown in FIG. 4;
  • FIG. 6 is a diagram of a flow of objects within a distributed processing system consistent with the present invention.
  • FIG. 7 is a flow diagram of steps performed in transmitting objects in a distributed system using loading of remote code for construction of an object in an implementation consistent with the present invention
  • FIG. 8 is a flow diagram of steps performed for deferring code loading and construction of objects when transmitting objects in a distributed system consistent with the present invention
  • FIG. 9 is a diagram of a distributed network illustrating event notification.
  • FIG. 10 is a flow chart of a process for event notification within a distributed network.
  • Systems consistent with the present invention efficiently transfer objects using a variant of an RPC or RMI, passing arguments and return values from one process to another process each of which may be on different machines. In such cases, it is desirable to defer reconstruction of the object and downloading of code associated with such object reconstruction until it is needed by the program.
  • machine is used in this context to refer to a physical machine or a virtual machine. Multiple virtual machines may exist on the same physical machine. Examples of RPC systems include distributed computed environment (DCE) RPC and Microsoft distributed common object model (DCOM) RPC.
  • DCE distributed computed environment
  • DCOM Microsoft distributed common object model
  • a self-describing stream a first-class entity in the system, meaning that it exists within a type system of a programming language and can be accessed and manipulated by instructions written in that language.
  • a stream is typically a sequence of characters, such as a bit pattern, capable of transmission, and a self-describing byte stream is a byte stream that contains enough information such that it can be converted back into the corresponding object.
  • An object called a “marshalled object” comprises the self-describing stream.
  • Such marshalled objects can typically be produced from any object that can be passed from one address space to another, and they can be stored, passed to other objects, or used to reconstruct an object of the original type on demand.
  • the advantage of using marshalled objects is that the reconstruction of an object is deferred until a process having access to the marshalled object directly invokes the creation of the object using the marshalled object. Any downloading of code required to operate on the object is deferred until the marshalled object is used to create a copy of the original object, which was previously used to produce the marshalled object.
  • RMI does not download the code required for reconstruction of the object. This may result in considerable efficiencies, both in time and in code storage space.
  • Event notification may occur through use of a marshalled object.
  • a machine registers with a device to receive notification of particular events within a distributed network.
  • the device transmits a request for registration along with a marshalled object to an event generator, which stores the marshalled object for possible later transmission.
  • the event generator sends notification of the event including the marshalled object to an event listener.
  • the event listener may reconstruct the marshalled object, which may contain information relating to the event.
  • the event listener may be the same as the device requesting notification.
  • Events include, for example, a change in the state or occurrence of an object.
  • More specific examples of events in a distributed system include, but are not limited to, the following: a “click” by a key or cursor-control device; an overlapping window on a display device; a device joining a network; a user logging onto a network; and particular user actions.
  • FIG. 3 illustrates an exemplary distributed processing system 300 which can be used in an implementation consistent with the present invention.
  • distributed processing system 300 contains three independent and heterogeneous platforms 301 , 302 , and 303 connected in a network configuration represented by network cloud 319 .
  • the composition and protocol of the network configuration represented by cloud 319 is not important as long as it allows for communication of the information between platforms 301 , 302 and 303 .
  • the use of just three platforms is merely for illustration and does not limit an implementation consistent with the present invention to the use of a particular number of platforms.
  • the specific network architecture is not crucial to embodiments consistent with this invention. For example, another network architecture that could be used in an implementation consistent with this invention would employ one platform as a network controller to which all the other platforms would be connected.
  • platforms 301 , 302 and 303 each include a processor 316 , 317 , and 318 respectively, and a memory, 304 , 305 , and 306 , respectively. Included within each memory 304 , 305 , and 306 , are applications 307 , 308 , and 309 , respectively, operating systems 310 , 311 , and 312 , respectively, and RMI components 313 , 314 , and 315 , respectively.
  • Applications 307 , 308 , and 309 can be applications or programs that are either previously written and modified to work with, or that are specially written to take advantage of, the services offered by an implementation consistent with the present invention. Applications 307 , 308 , and 309 invoke operations to be performed in accordance with an implementation consistent with this invention.
  • Operating systems 310 , 311 , and 312 are typically standard operating systems tied to the corresponding processors 316 , 317 , and 318 , respectively.
  • the platforms 301 , 302 , and 303 can be heterogenous.
  • platform 301 has an UltraSparc® microprocessor manufactured by Sun Microsystems, Inc. as processor 316 and uses a Solaris® operating system 310 .
  • Platform 302 has a MIPS microprocessor manufactured by Silicon Graphics Corp. as processor 317 and uses a Unix operating system 311 .
  • platform 303 has a Pentium microprocessor manufactured by Intel Corp. as processor 318 and uses a Microsoft Windows 95 operating system 312 .
  • An implementation consistent with the present invention is not so limited and could accommodate homogenous platforms as well.
  • Sun, Sun Microsystems, Solaris, Java, and the Sun Logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. UltraSparc and all other SPARC trademarks are used under license and are trademarks of SPARC International, Inc. in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.
  • Memories 304 , 305 , and 306 serve several functions, such as general storage for the associated platform. Another function is to store applications 307 , 308 , and 309 , RMI components 313 , 314 , and 315 , and operating systems 310 , 311 , and 312 during execution by the respective processor 316 , 317 , and 318 . In addition, portions of memories 304 , 305 , and 306 may constitute shared memory available to all of the platforms 301 , 302 , and 303 in network 319 . Note that RMI components 313 , 314 , and 315 operate in conjunction with a JVM, which is not shown for the purpose of simplifying the figure.
  • Systems and methods consistent with the present invention may also operate within a particular distributed system 400 , which will be described with reference to FIGS. 4 and 5.
  • This distributed system 400 is comprised of various components, including hardware and software, to (1) allow users of the system to share services and resources over a network of many devices; (2) provide programmers with tools and programming patterns that allow development of robust, secured distributed systems; and (3) simplify the task of administering the distributed system.
  • distributed system 400 utilizes the Java programming environment to allow both code and data to be moved from device to device in a seamless manner. Accordingly, distributed system 400 is layered on top of the Java programming environment and exploits the characteristics of this environment, including the security offered by it and the strong typing provided by it.
  • distributed system 400 of FIGS. 4 and 5 different computers and devices are federated into what appears to the user to be a single system.
  • distributed system 400 provides the simplicity of access and the power of sharing that can be provided by a single system without giving up the flexibility and personalized response of a personal computer or workstation.
  • Distributed system 400 may contain thousands of devices operated by users who are geographically disperse, but who agree on basic notions of trust, administration, and policy.
  • a “service” refers to a resource, data, or functionality that can be accessed by a user, program, device, or another service and that can be computational, storage related, communication related, or related to providing access to another user.
  • Examples of services provided as part of a Djinn include devices, such as printers, displays, and disks; software, such as programs or utilities; information, such as databases and files; and users of the system.
  • Both users and devices may join a Djinn.
  • the user or device When joining a Djinn, the user or device adds zero or more services to the Djinn and may access, subject to security constraints, any one of the services it contains.
  • devices and users federate into a Djinn to share access to its services.
  • the services of the Djinn appear programmatically as objects of the Java programming environment, which may include other objects, software components written in different programming languages, or hardware devices.
  • a service has an interface defining the operations that can be requested of that service, and the type of the service determines the interfaces that make up that service.
  • Distributed system 400 is comprised of computer 402 , a computer 404 , and a device 406 interconnected by a network 408 .
  • Device 406 may be any of a number of devices, such as a printer, fax machine, storage device, computer, or other devices.
  • Network 408 may be a local area network, wide area network, or the Internet. Although only two computers and one device are depicted as comprising distributed system 400 , one skilled in the art will appreciate that distributed system 400 may include additional computers or devices.
  • FIG. 5 depicts computer 402 in greater detail to show a number of the software components of distributed system 400 .
  • Computer 402 includes a memory 502 , a secondary storage device 504 , a central processing unit (CPU) 506 , an input device 508 , and a video display 510 .
  • Memory 502 includes a lookup service 512 , a discovery server 514 , and a Java runtime system 516 .
  • the Java runtime system 516 includes the Java RMI system 518 and a JVM 520 .
  • Secondary storage device 504 includes a Java space 522 .
  • the Java runtime system 516 includes the Java API libraries, allowing programs running on top of the Java runtime system to access, in a platform-independent manner, various system functions, including windowing capabilities and networking capabilities of the host operating system. Since the Java API libraries provides a single common API across all operating systems to which the Java runtime system is ported, the programs running on top of a Java runtime system run in a platform-independent manner, regardless of the operating system or hardware configuration of the host platform.
  • the Java runtime system 516 is provided as part of the Java software development kit available from Sun Microsystems, Inc. of Mountain View, Calif.
  • JVM 520 also facilitates platform independence. JVM 520 acts like an abstract computing machine, receiving instructions from programs in the form of bytecodes and interpreting these bytecodes by dynamically converting them into a form for execution, such as object code, and executing them.
  • RMI 518 facilitates remote method invocation by allowing objects executing on one computer or device to invoke methods of an object on another computer or device. Both RMI and the JVM are also provided as part of the Java software development kit.
  • Lookup service 512 defines the services that are available for a particular Djinn. That is, there may be more than one Djinn and, consequently, more than one lookup service within distributed system 400 .
  • Lookup service 512 contains one object for each service within the Djinn, and each object contains various methods that facilitate access to the corresponding service.
  • Lookup service 512 is described in U.S. patent application entitled “Method and System for Facilitating Access to a Lookup Service,” which was previously incorporated herein by reference.
  • Discovery server 514 detects when a new device is added to distributed system 400 , during a process known as boot and join (or discovery), and when such a new device is detected, the discovery server passes a reference to lookup service 512 to the new device so that the new device may register its services with the lookup service and become a member of the Djinn. After registration, the new device becomes a member of the Djinn, and as a result, it may access all the services contained in lookup service 512 .
  • boot and join is described in U.S.
  • a Java space 522 is an object repository used by programs within distributed system 400 to store objects. Programs use a Java space 522 to store objects persistently as well as to make them accessible to other devices within distributed system 400 .
  • Java spaces are described in U.S. patent application Ser. No. 08/971,529, entitled “Database System Employing Polymorphic Entry and Entry Matching,” assigned to a common assignee, and filed on Nov. 17, 1997, which is incorporated herein by reference.
  • an exemplary distributed system 400 may contain many lookup services, discovery servers, and Java spaces.
  • FIG. 6 is a diagram of an object-oriented distributed system 600 connecting machines 601 , 602 , and 603 , such as computers or virtual machines executing on one or more computers, or the machines described with reference to FIG. 3.
  • Transmitting machine 601 includes a memory 604 storing objects such as objects 605 and 606 , and RMI 607 for performing processing on the objects.
  • RMI 607 uses code 609 for converting object 605 into a marshalled object that is transmitted as a byte stream 608 to machine 602 .
  • Part of this conversion includes adding information so that a receiving machine 602 can reconstruct the object.
  • a receiving machine typically requires the object's state and a description of its type because the object's code is already present on all network machines.
  • machine 601 uses RMI 607 to provide more flexibility, allowing code to be moved when necessary along with information or the object's state and type.
  • a transmitting machine includes in the marshalled object an identification of the type of object transmitted, the data constituting the state of the object, and a network-accessible location in the form of a URL for code that is associated with the object.
  • Machine 602 When receiving machine 602 receives byte stream 608 , it identifies the type of transmitted object.
  • Machine 602 contains its own RMI 610 and code 611 for processing of objects. If byte stream 608 contains a marshalled object, machine 602 may create a new object 614 using the object type identified in the marshalled object, the state information, and code for the object.
  • Object 614 is a copy of object 605 and is stored in memory 613 of machine 602 . If code 612 is not resident or available on machine 602 and the marshalled object does not contain the code, RMI 610 uses the URL from the marshalled object to locate the code and transfer a copy of the code to machine 602 .
  • Code 612 is generally only required if the object is unmarshalled. Because the code is in bytecode format and is therefore portable, the receiving machine can load the code into RMI 610 to reconstruct the object. Thus, machine 602 can reconstruct an object of the appropriate type even if that kind of object has not been present on the machine before.
  • Machine 602 may also convert object 614 into byte stream 615 for transmission to a third machine 603 , which contains its own RMI 618 and code 619 for processing objects.
  • RMI 618 using code 620 for the object, converts byte stream 615 into a corresponding object 616 , which it stores in memory 617 .
  • Object 616 is a copy of object 605 . If code 620 for the object is not resident or available, machine 603 requests the code from another machine using the URL, as described above.
  • Machine 602 may alternatively store the marshalled object as a byte stream without reconstructing the object. It may then transmit the byte stream to machine 603 .
  • a marshalled object is a container for an object that allows that object to be passed as a parameter in RMI call, but postpones conversion of the marshalled object at the receiving machine until a program executing on the receiving machine explicitly requests the object via a call to the marshalled object.
  • a container is an envelope that includes the data and either the code or a reference to the code for the object, and that holds the object for transmission.
  • the serializable object contained in the marshalled object is typically serialized and deserialized when requested with the same semantics as parameters passed in RMI calls.
  • Serialization is a process of converting an in-memory representation of an object into a corresponding self-describing byte stream.
  • Deserialization is a process of converting a self-describing byte stream into the corresponding object.
  • the object is placed inside a marshalled object container and when a URL is used to locate code for the object, the URL is added to the container.
  • the URL is added to the container.
  • Table 1 provides an exemplary class definition in the Java programming language for a marshalled object consistent with the present invention.
  • a marshalled object may be embodied within an article of manufacture specifying a representation of the object stored in a computer-readable storage medium.
  • a marshalled object's constructor takes a serializable object (obj) as its single argument and holds the marshalled representation of the object in a byte stream.
  • the marshalled representation of the object preserves the semantics of objects that are passed in RMI calls: each class in the stream is typically annotated with either the object's code or a URL to the code so that when the object is reconstructed by a call to a “get” method, the bytecodes for each class can be located and loaded, and remote objects are replaced with their proxy stubs.
  • the “get” method is a method called by a program to execute a process of unmarshalling, which is reconstruction of an object from a marshalled object using a self-describing byte stream (the marshalled object), and a process to obtain the necessary code for that process.
  • a proxy stub is a reference to a remote object for use in reconstructing an object.
  • the “get” method preferably always reconstructs a new copy of the contained object from its marshalled form.
  • the internal representation is deserialized with the same semantics used for unmarshalling parameters for RMI calls.
  • the deserialization of the object's representation loads class codes, if not available locally, using the URL annotation embedded in the serialized stream for the object.
  • the hash code of the marshalled representation of an object is defined to be equivalent to the hash code for the object itself.
  • a hash code is used in hash tables to perform fast look-ups of information, which is known in the art.
  • the equals method will return true if the marshalled representation of the objects being compared are equivalent.
  • An equals method verifies reconstruction by determining if a reconstructed object is the same as the original object, and such methods are known in the Java programming language.
  • FIG. 7 is a flow diagram of steps 700 preferably performed in transmitting objects in a distributed system consistent with the present invention.
  • a machine receives a byte stream (step 701 ), which includes data for the object, information identifying the type of object, and optionally a URL for the code that is associated with the object.
  • the receiving machine determines if the code for the object is resident or available (step 702 ). If it is available, the machine preferably uses RMI for reconstructing the object from the byte stream and resident code (step 704 ). If the code is not resident, the machine uses the URL from the byte stream to request the code from another machine located at a network accessible location, and that machine returns a copy of the code (step 703 ).
  • the object can also be transmitted in the form of a byte stream to another machine (step 705 ).
  • FIG. 8 is a flow diagram of steps 800 preferably performed for deferring code loading and construction of objects when transmitting marshalled objects in a distributed system consistent with the present invention.
  • a machine receives a byte stream (step 801 ), which includes data for the object, information identifying the type of object, and optionally a URL for the code that is associated with the object.
  • the machine determines if the byte stream is a marshalled object (step 802 ). If it is not such an object, the machine performs normal processing of the byte stream (step 803 ). Otherwise, if the received byte stream represents a marshalled object, the machine holds the marshalled object for later use in response to a get method invoked by a process on the receiving machine. If the receiving machine determines that the object is to be transmitted to another machine (step 804 ), it simply transmits the byte stream without reconstructing the object. If the machine uses the object, it performs reconstruction of the object using its RMI and associated code (step 805 ).
  • the reconstruction code for the object uses a URL to request and obtain the code (step 806 ), as described above.
  • the machine determines if it needs to transmit the object to another machine (step 807 ). If the object is destined for another machine, it is transmitted as a byte stream (step 808 ).
  • a marshalled object provides for more efficient transfer of objects in a distributed system. If an object is needed by a machine, it can be reconstructed, and if the machine does not need to use the object, it can transmit the marshalled object without reconstructing it.
  • FIG. 9 is a diagram of a distributed network 900 illustrating event notification.
  • Network 900 may use the machines described with reference to FIGS. 3, 4, and 5 .
  • Network 900 includes a remote event listener 901 having RMI 902 and object 903 , a machine 904 having RMI 905 and object 906 , and an event generator 907 having RMI 908 and object 909 for providing event notification.
  • Machine 904 may be the same as remote event listener 901 , as indicated by the dashed line, or they may be separate machines.
  • Machine 904 desiring notification of a particular network event, registers with RMI 908 by transmitting a request for event notification including or associated with a marshalled object 912 .
  • Event generator 907 stores the marshalled object for possible later transmission.
  • RMI 908 detects an occurrence of the event, it transmits notification of the event along with the marshalled object 913 to remote event listener 901 .
  • Remote event listener 901 may make a call to code server 910 in order to obtain code 911 for reconstructing the marshalled object, which may contain information relating to the event.
  • a code server is an entity and process that has access to code and responds to requests for a particular type or class of object and returns code for that object.
  • a code server may be located within machine 901 or on another machine. Also, the code may be resident on the same platform as the code server or on a separate platform. After registration, remote event listener 901 may provide indications of the particular event when detected.
  • FIG. 10 is a flow chart of a process 1000 or event notification within a distributed network, such as network 900 .
  • a machine sends a registration request including a marshalled object to a remote event generator (step 1001 ), which stores the marshalled object for possible later transmission (step 1002 ).
  • the event generator determines if the event occurred (step 1003 ), and, if it detects such an occurrence, it sends notification of the event including the stored marshalled object to an event listener machine (step 1004 ).
  • the event generator determines, based on particular criteria or system requirements, if it is to continue providing notification of occurrences of the event (step 1005 ). If so, it continues to determine if the event occurred.
  • These steps may use, for example, interfaces and class definitions written in the Java programming language shown in Tables 1-5 provided in this specification.
  • Table 2 provides an example of an interface in the Java programming language for implementing a remote event listener.
  • RemoteEventListener extends Remote, java.util.EventListener ⁇ void notify(RemoteEvent theEvent) throws EventUnknownException, RemoteException; ⁇
  • the notify method has a single parameter of type “RemoteEvent” that is used during operation to encapsulate the information passed as part of a notification.
  • Table 3 provides an example of a definition for the public part of the “RemoteEvent” class definition.
  • TABLE 3 public class RemoteEvent extends EventObject ⁇ public RemoteEvent (Object evSource, long evIdNo, long evSeqNo) public Object getSource ( ); public long getID( ); public long getSeqNo ( ); public MarshalledObject getRegistrationObject ( ); ⁇
  • the abstract state contained in a “RemoteEvent” object includes a reference to the object in which the event occurred, a “long” which identifies the kind of event relative to the object in which the event occurred, and a “long” which indicates the sequence number (“SeqNo”) of this instance of the event kind.
  • the sequence number obtained from the “RemoteEvent” object is an increasing value that may provide an indication concerning the number of occurrences of this event relative to an earlier sequence number.
  • Table 4 provides an example of an interface in the Java programming language for an event generator.
  • EventGenerator extends Remote ⁇ public EventRegistration register (long evId, MarshalledObject handback, RemoteEventListener toInform, long leasePeriod) throws EventUnknownException, RemoteException; ⁇
  • the register method shown in Table 4 allows registration of interest in the occurrence of an event inside an object. While executing this method, a JVM receives an “evId,” which is a long integer used to identify the class of events; an object that is transmitted back as part of the notification; a reference to a “RemoteEventListener” object; and a long integer indicating the leasing period for the interest registration. If an “evId” is provided to this call that is not recognized by the event generator object, the JVM signals an error. In the Java programming language, a JVM is said to “throw” an “EventUnknownException” to signal that error.
  • the second argument of the register method is a marshalled object that is to be transmitted back as part of the notification generated when an event of the appropriate type occurs.
  • the third argument of the register method is a remote event listener object that receives any notifications of instances of the event kind occurring. This argument may be the object that is registering interest, or it may be another remote event listener such as a third-party event handler or notification “mailbox.”
  • the final argument to the register method is a “long” indicating the requested duration of the registration, referred to as the “lease.”
  • the return value of the register method is an object of the event registration class definition. This object contains a “long” identifying the kind of event in which interest was registered relative to the object granting the registration, a reference to the object granting the registration, and a lease object containing information concerning the lease period.
  • Table 5 provides an example of a class definition in the Java programming language for event registration.
  • public class EventRegistration implements java.io.Serializable ⁇ public EventRegistration (long eventNum, Remote registerWith, Lease eventLease, long currentSeqNum); public long getEventID ( ); public Object getEventSource ( ); public LeasegetLease ( ); public long currentSeqNum ( ); ⁇
  • the “getEventID” method returns the identifier of the event in which interest was registered, which combined with the return value of the “getEventSource” method uniquely identifies the kind of event. This information is provided to third-party repositories to allow them to recognize the event and route it correctly.
  • the “getLease” method returns the lease object for this registration and is used in lease maintenance.
  • the “currentSeqNo” method returns the value of the sequence number on the event kind that was current when the registration was granted, allowing comparison with the sequence number in any subsequent notifications.
  • a “toString” method may be used with this class definition to return a human-readable string containing the information making up the state of the object.
  • Machines implementing the steps shown in FIGS. 7, 8, and 10 may include computer processors for performing the functions, as shown in FIGS. 3, 4, and 5 . They may include modules or programs configured to cause the processors to perform the above functions. They may also include computer program products stored in a memory.
  • the computer program products may include a computer-readable medium or media having computer-readable code embodied therein for causing the machines to perform functions described above.
  • the media may include a computer data signal embodied in a carrier wave and representing sequences of instructions which, when executed by a processor, cause the processor to securely address a peripheral device at an absolute address by performing the method described in this specification.
  • the media may also include data structures for use in performing the method described in this specification.

Abstract

Event notification in a distributed system using an object maintained in serialized form, referred to as a marshalled object. For event notification, a machine registers with a device to receive notification of particular events within a network, and a marshalled object is transmitted with a registration request.

Description

    REFERENCE TO RELATED APPLICATIONS
  • The present application is a continuation-in-part of U.S. patent application Ser. No. 08/950,756, filed on Oct. 15, 1997, and entitled “Deferred Reconstruction of Objects and Remote Loading in a Distributed System,” which is incorporated herein by reference. [0001]
  • The following identified U.S. patent applications are relied upon and are incorporated by reference in this application as if fully set forth. [0002]
  • Provisional U.S. patent application Ser. No.______, entitled “Distributed Computing System,” filed on Feb. 26, 1998. [0003]
  • U.S. patent application Ser. No.______, entitled “Method and System for Leasing Storage,” bearing attorney docket no. 06502.0011-01000, and filed on the same date herewith. [0004]
  • U.S. patent application Ser. No.______, entitled “Method, Apparatus, and Product for Leasing of Delegation Certificates in a Distributed System,” bearing attorney docket no. 06502.0011-02000, and filed on the same date herewith. [0005]
  • U.S. patent application Ser. No.______, entitled “Method, Apparatus and Product for Leasing of Group Membership in a Distributed System,” bearing attorney docket no. 06502.0011-03000, and filed on the same date herewith. [0006]
  • U.S. patent application Ser. No.______, entitled “Leasing for Failure Detection,” bearing attorney docket no. 06502.0011-04000, and filed on the same date herewith. [0007]
  • U.S. patent application Ser. No.______, entitled “Method for Transporting Behavior in Event Based System,” bearing attorney docket no. 06502.0054-00000, and filed on the same date herewith. [0008]
  • U.S. patent application Ser. No.______, entitled “Methods and Apparatus for Remote Method Invocation,” bearing attorney docket no. 06502.0102-00000, and filed on the same date herewith. [0009]
  • U.S. patent application Ser. No.______, entitled “Method and System for Deterministic Hashes to Identify Remote Methods,” bearing attorney docket no. 06502.0103-00000, and filed on the same date herewith. [0010]
  • U.S. patent application Ser. No.______, entitled “Method and Apparatus for Determining Status of Remote Objects in a Distributed System,” bearing attorney docket no. 06502.0104-00000, and filed on the same date herewith. [0011]
  • U.S. patent application Ser. No.______, entitled “Downloadable Smart Proxies for Performing Processing Associated with a Remote Procedure Call in a Distributed System,” bearing attorney docket no. 06502.0105-00000, and filed on the same date herewith. [0012]
  • U.S. patent application Ser. No.______, entitled “Suspension and Continuation of Remote Methods,” bearing attorney docket no. 06502.0106-00000, and filed on the same date herewith. [0013]
  • U.S. patent application Ser. No.______, entitled “Method and System for Multi-Entry and Multi-Template Matching in a Database,” bearing attorney docket no. 06502.0107-00000, and filed on the same date herewith. [0014]
  • U.S. patent application Ser. No.______, entitled “Method and System for In-Place Modifications in a Database,” bearing attorney docket no. 06502.0108, and filed on the same date herewith. [0015]
  • U.S. patent application Ser. No.______, entitled “Method and System for Typesafe Attribute Matching in a Database,” bearing attorney docket no. 06502.0109-00000, and filed on the same date herewith. [0016]
  • U.S. patent application Ser. No.______, entitled “Dynamic Lookup Service in a Distributed System,” bearing attorney docket no. 06502.0110-00000, and filed on the same date herewith. [0017]
  • U.S. patent application Ser. No.______, entitled “Apparatus and Method for Providing Downloadable Code for Use in Communicating with a Device in a Distributed System,” bearing attorney docket no. 06502.0112-00000, and filed on the same date herewith. [0018]
  • U.S. patent application Ser. No.______, entitled “Method and System for Facilitating Access to a Lookup Service,” bearing attorney docket no. 06502.0113-00000, and filed on the same date herewith. [0019]
  • U.S. patent application Ser. No.______, entitled “Apparatus and Method for Dynamically Verifying Information in a Distributed System,” bearing attorney docket no. 06502.0114-00000, and filed on the same date herewith. [0020]
  • U.S. patent application Ser. No. 09/030,840, entitled “Method and Apparatus for Dynamic Distributed Computing Over a Network,” and filed on Feb. 26, 1998. [0021]
  • U.S. patent application Ser. No.______, entitled “An Interactive Design Tool for Persistent Shared Memory Spaces,” bearing attorney docket no. 06502.0116-00000, and filed on the same date herewith. [0022]
  • U.S. patent application Ser. No.______, entitled “Polymorphic Token-Based Control,” bearing attorney docket no. 06502.0117-00000, and filed on the same date herewith. [0023]
  • U.S. patent application Ser. No.______, entitled “Stack-Based Access Control,” bearing attorney docket no. 06502.0118-00000, and filed on the same date herewith. [0024]
  • U.S. patent application Ser. No.______, entitled “Stack-Based Security Requirements,” bearing attorney docket no. 06502.0119-00000, and filed on the same date herewith. [0025]
  • U.S. patent application Ser. No.______, entitled “Per-Method Designation of Security Requirements,” bearing attorney docket no. 06502.0120-00000, and filed on the same date herewith.[0026]
  • FIELD OF THE INVENTION
  • The present invention relates to a system and method for transmitting objects between machines in a distributed system and more particularly relates to deferred reconstruction of objects for event notification in a distributed system. [0027]
  • BACKGROUND OF THE INVENTION
  • Distributed programs which concentrate on point-to-point data transmission can often be adequately and efficiently handled using special-purpose protocols for remote terminal access and file transfer. Such protocols are tailored specifically to the one program and do not provide a foundation on which to build a variety of distributed programs (e.g., distributed operating systems, electronic mail systems, computer conferencing systems, etc.). [0028]
  • While conventional transport services can be used as the basis for building distributed programs, these services exhibit many organizational problems, such as the use of different data types in different machines, lack of facilities for synchronization, and no provision for a simple programming paradigm. [0029]
  • Distributed systems usually contain a number of different types of machines interconnected by communications networks. Each machine has its own internal data types, its own address alignment rules, and its own operating system. This heterogeneity causes problems when building distributed systems. As a result, program developers must include in programs developed for such heterogeneous distributed systems the capability of dealing with ensuring that information is handled and interpreted consistently on different machines. [0030]
  • However, one simplification is afforded by noting that a large proportion of programs use a request and response interaction between processes where the initiator (i.e., program initiating a communication) is blocked waiting until the response is returned and is thus idle during this time. This can be modeled by a procedure call mechanism between processes. One such mechanism is referred to as the remote procedure call (RPC). [0031]
  • RPC is a mechanism for providing synchronized communication between two processes (e.g., program, applet, etc.) running on the same machine or different machines. In a simple case, one process, e.g., a client program, sends a message to another process, e.g., a server program. In this case, it is not necessary for the processes to be synchronized either when the message is sent or received. It is possible for the client program to transmit the message and then begin a new activity, or for the server program's environment to buffer the incoming message until the server program is ready to process a new message. [0032]
  • RPC, however, imposes constraints on synchronism because it closely models the local procedure call, which requires passing parameters in one direction, blocking the calling process (i.e., the client program) until the called procedure of the server program is complete, and then returning a response. RPC thus involves two message transfers, and the synchronization of the two processes for the duration of the call. [0033]
  • The RPC mechanism is usually implemented in two processing parts using the local procedure call paradigm, one part being on the client side and the other part being on the server side. Both of these parts will be described below with reference to FIG. 1. [0034]
  • FIG. 1 is a diagram illustrating the flow of call information using an RPC mechanism. As shown in FIG. 1, a [0035] client program 100 issues a call (step 102). The RPC mechanism 101 then packs the call as arguments of a call packet (step 103), which the RPC mechanism 101 then transmits to a server program 109 (step 104). The call packet also contains information to identify the client program 100 that first sent the call. After the call packet is transmitted (step 104), the RPC mechanism 101 enters a wait state during which it waits for a response from the server program 109.
  • The [0036] RPC mechanism 108 for the server program 109 (which may be the same RPC mechanism as the RPC mechanism 101 when the server program 109 is on the same platform as the client program 100) receives the call packet (step 110), unpacks the arguments of the call from the call packet (step 111), identifies, using the call information, the server program 109 to which the call was addressed, and provides the call arguments to the server program 169.
  • The server program receives the call (step [0037] 112), processes the call by invoking the appropriate procedure (step 115), and returns a response to the RPC mechanism 108 (step 116). The RPC mechanism 108 then packs the response in a response packet (step 114) and transmits it to the client program 100 (step 113).
  • Receiving the response packet (step [0038] 107) triggers the RPC mechanism 101 to exit the wait state and unpack the response from the response packet (step 106). RPC 101 then provides the response to the client program 100 in response to the call (step 105). This is the process flow of the typical RPC mechanism modeled after the local procedure call paradigm. Since the RPC mechanism uses the local procedure call paradigm, the client program 100 is blocked at the call until a response is received. Thus, the client program 100 does not continue with its own processing after sending the call; rather, it waits for a response from the server program 109.
  • The Java™ programming language is an object-oriented programming language that is typically compiled into a platform-independent format, using a bytecode instruction set, which can be executed on any platform supporting the Java virtual machine (JVM). This language is described, for example, in a text entitled “The Java Language Specification” by James Gosling, Bill Joy, and Guy Steele, Addison-Wesley, 1996, which is incorporated herein by reference. The JVM is described, for example, in a text entitled “The Java Virtual Machine Specification,” by Tim Lindholm and Frank Yellin, Addison Wesley, 1996, which is incorporated herein by reference. Java and Java-based trademarks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. [0039]
  • Because the JVM may be implemented on any type of platform, implementing distributed programs using the JVM significantly reduces the difficulties associated with developing programs for heterogenous distributed systems. Moreover, the JVM uses a Java remote method invocation (RMI) system that enables communication among programs of the system. RMI is explained in, for example, the following document, which is incorporated herein by reference: Remote Method Invocation Specification, Sun Microsystems, Inc. (1997), which is available via universal resource locator (URL) http://www.javasoft.com/products/jdk/1.1/docs/guide/rmi/spec/rmiTOC.doc.html. [0040]
  • FIG. 2 is a diagram illustrating the flow of objects in an object-oriented distributed [0041] system 200 including machines 201 and 202 for transmitting and receiving method invocations using the JVM. In system 200, machine 201 uses RMI 205 for responding to a call for object 203 by converting the object into a byte stream 207 including an identification of the type of object transmitted and data constituting the object. While machine 201 is responding to the call for object 203, a process running on the same or another machine in system 200 may continue operation without waiting for a response to its request.
  • [0042] Machine 202 receives the byte stream 207. Using RMI 206, machine 202 automatically converts it into the corresponding object 204, which is a copy of object 203 and which makes the object available for use by a program executing on machine 202. Machine 202 may also transmit the object to another machine by first converting the object into a byte stream and then sending it to the third machine, which also automatically converts the byte stream into the corresponding object.
  • The automatic reconstruction of the objects from the byte stream in this manner sometimes requires unnecessary processing. For example, there are times when a call is made that does not require actual or immediate interaction with the object, both of which require conversion of the byte stream to object form. Instead, a call may require passing the object to another call or storing it for later use. In this situation, the reconstruction of the object on an intermediate machine is unnecessary, especially if the object is to be transmitted to another machine. Examples of such a situation include transmission of objects for notification of events in a distributed system. Accordingly, it is desirable to more efficiently transmit objects in a distributed system without the unneeded conversion of a byte stream to an object on intermediate machines that have no use for the object, or the premature conversion of the byte stream before a process on the receiving machine requires access to the object. [0043]
  • SUMMARY OF THE INVENTION
  • A method consistent with the present invention specifies an object associated with a request for notification of a particular event within a distributed system. The object is converted into a stream containing a self-describing form of the object, and the stream is provided for selective transmission to a machine where the object is reconstructed by accessing program code identified in the stream upon occurrence of the event. [0044]
  • Another method consistent with the present invention receives at a first machine a stream containing a self-describing form of an object associated with a request for notification of a particular event within a distributed system. The method includes determining whether to send the stream to a second machine and selectively sending the stream to the second machine for reconstruction of the object by accessing program code identified in the stream, the first machine providing notification of the event. [0045]
  • An apparatus consistent with the present invention specifies an object associated with a request for notification of a particular event within a distributed system. The apparatus converts the object into a stream containing a self-describing form of the object and provides the stream for selective transmission to a machine where the object is reconstructed by accessing program code identified in the stream upon occurrence of the event. [0046]
  • Another apparatus consistent with the present invention receives at a first machine a stream containing a self-describing form of an object associated with a request for notification of a particular event within a distributed system. The apparatus determines whether to send the stream to a second machine and selectively sends the stream to the second machine for reconstruction of the object by accessing program code identified in the stream, the first machine providing notification of the event.[0047]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The accompanying drawings are incorporated in and constitute a part of this specification and, together with the description, explain the advantages and principles of the invention. In the drawings, [0048]
  • FIG. 1 is a diagram illustrating the flow of call information using an RPC mechanism; [0049]
  • FIG. 2 is a diagram illustrating the transmission of objects in an object-oriented distributed system; [0050]
  • FIG. 3 is a diagram of an exemplary distributed processing system that can be used in an implementation consistent with the present invention; [0051]
  • FIG. 4 is a diagram of an exemplary distributed system infrastructure; [0052]
  • FIG. 5 is a diagram of a computer in a distributed system infrastructure shown in FIG. 4; [0053]
  • FIG. 6 is a diagram of a flow of objects within a distributed processing system consistent with the present invention; [0054]
  • FIG. 7 is a flow diagram of steps performed in transmitting objects in a distributed system using loading of remote code for construction of an object in an implementation consistent with the present invention; [0055]
  • FIG. 8 is a flow diagram of steps performed for deferring code loading and construction of objects when transmitting objects in a distributed system consistent with the present invention; [0056]
  • FIG. 9 is a diagram of a distributed network illustrating event notification; and [0057]
  • FIG. 10 is a flow chart of a process for event notification within a distributed network.[0058]
  • DETAILED DESCRIPTION Overview
  • Systems consistent with the present invention efficiently transfer objects using a variant of an RPC or RMI, passing arguments and return values from one process to another process each of which may be on different machines. In such cases, it is desirable to defer reconstruction of the object and downloading of code associated with such object reconstruction until it is needed by the program. The term “machine” is used in this context to refer to a physical machine or a virtual machine. Multiple virtual machines may exist on the same physical machine. Examples of RPC systems include distributed computed environment (DCE) RPC and Microsoft distributed common object model (DCOM) RPC. [0059]
  • An example of how this is accomplished is by making a self-describing stream a first-class entity in the system, meaning that it exists within a type system of a programming language and can be accessed and manipulated by instructions written in that language. A stream is typically a sequence of characters, such as a bit pattern, capable of transmission, and a self-describing byte stream is a byte stream that contains enough information such that it can be converted back into the corresponding object. [0060]
  • An object called a “marshalled object” comprises the self-describing stream. Such marshalled objects can typically be produced from any object that can be passed from one address space to another, and they can be stored, passed to other objects, or used to reconstruct an object of the original type on demand. The advantage of using marshalled objects is that the reconstruction of an object is deferred until a process having access to the marshalled object directly invokes the creation of the object using the marshalled object. Any downloading of code required to operate on the object is deferred until the marshalled object is used to create a copy of the original object, which was previously used to produce the marshalled object. [0061]
  • Accordingly, in cases where the object is not used, but rather is stored for later retrieval or passed along to another process, RMI does not download the code required for reconstruction of the object. This may result in considerable efficiencies, both in time and in code storage space. [0062]
  • Event notification, for example, may occur through use of a marshalled object. For event notification, a machine registers with a device to receive notification of particular events within a distributed network. The device transmits a request for registration along with a marshalled object to an event generator, which stores the marshalled object for possible later transmission. If the event occurs, the event generator sends notification of the event including the marshalled object to an event listener. The event listener may reconstruct the marshalled object, which may contain information relating to the event. The event listener may be the same as the device requesting notification. Events include, for example, a change in the state or occurrence of an object. More specific examples of events in a distributed system include, but are not limited to, the following: a “click” by a key or cursor-control device; an overlapping window on a display device; a device joining a network; a user logging onto a network; and particular user actions. [0063]
  • Distributed Processing System
  • FIG.[0064] 3 illustrates an exemplary distributed processing system 300 which can be used in an implementation consistent with the present invention. In FIG. 3, distributed processing system 300 contains three independent and heterogeneous platforms 301, 302, and 303 connected in a network configuration represented by network cloud 319. The composition and protocol of the network configuration represented by cloud 319 is not important as long as it allows for communication of the information between platforms 301, 302 and 303. In addition, the use of just three platforms is merely for illustration and does not limit an implementation consistent with the present invention to the use of a particular number of platforms. Further, the specific network architecture is not crucial to embodiments consistent with this invention. For example, another network architecture that could be used in an implementation consistent with this invention would employ one platform as a network controller to which all the other platforms would be connected.
  • In the implementation of distributed [0065] processing system 300, platforms 301, 302 and 303 each include a processor 316, 317, and 318 respectively, and a memory, 304, 305, and 306, respectively. Included within each memory 304, 305, and 306, are applications 307, 308, and 309, respectively, operating systems 310, 311, and 312, respectively, and RMI components 313, 314, and 315, respectively.
  • [0066] Applications 307, 308, and 309 can be applications or programs that are either previously written and modified to work with, or that are specially written to take advantage of, the services offered by an implementation consistent with the present invention. Applications 307, 308, and 309 invoke operations to be performed in accordance with an implementation consistent with this invention.
  • [0067] Operating systems 310, 311, and 312 are typically standard operating systems tied to the corresponding processors 316, 317, and 318, respectively. The platforms 301, 302, and 303 can be heterogenous. For example, platform 301 has an UltraSparc® microprocessor manufactured by Sun Microsystems, Inc. as processor 316 and uses a Solaris® operating system 310. Platform 302 has a MIPS microprocessor manufactured by Silicon Graphics Corp. as processor 317 and uses a Unix operating system 311. Finally, platform 303 has a Pentium microprocessor manufactured by Intel Corp. as processor 318 and uses a Microsoft Windows 95 operating system 312. An implementation consistent with the present invention is not so limited and could accommodate homogenous platforms as well.
  • Sun, Sun Microsystems, Solaris, Java, and the Sun Logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. UltraSparc and all other SPARC trademarks are used under license and are trademarks of SPARC International, Inc. in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. [0068]
  • [0069] Memories 304, 305, and 306 serve several functions, such as general storage for the associated platform. Another function is to store applications 307, 308, and 309, RMI components 313, 314, and 315, and operating systems 310, 311, and 312 during execution by the respective processor 316, 317, and 318. In addition, portions of memories 304, 305, and 306 may constitute shared memory available to all of the platforms 301, 302, and 303 in network 319. Note that RMI components 313, 314, and 315 operate in conjunction with a JVM, which is not shown for the purpose of simplifying the figure.
  • Distributed System Infrastructure
  • Systems and methods consistent with the present invention may also operate within a particular distributed [0070] system 400, which will be described with reference to FIGS. 4 and 5. This distributed system 400 is comprised of various components, including hardware and software, to (1) allow users of the system to share services and resources over a network of many devices; (2) provide programmers with tools and programming patterns that allow development of robust, secured distributed systems; and (3) simplify the task of administering the distributed system. To accomplish these goals, distributed system 400 utilizes the Java programming environment to allow both code and data to be moved from device to device in a seamless manner. Accordingly, distributed system 400 is layered on top of the Java programming environment and exploits the characteristics of this environment, including the security offered by it and the strong typing provided by it.
  • In distributed [0071] system 400 of FIGS. 4 and 5, different computers and devices are federated into what appears to the user to be a single system. By appearing as a single system, distributed system 400 provides the simplicity of access and the power of sharing that can be provided by a single system without giving up the flexibility and personalized response of a personal computer or workstation. Distributed system 400 may contain thousands of devices operated by users who are geographically disperse, but who agree on basic notions of trust, administration, and policy.
  • Within an exemplary distributed system are various logical groupings of services provided by one or more devices, and each such logical grouping is known as a Djinn. A “service” refers to a resource, data, or functionality that can be accessed by a user, program, device, or another service and that can be computational, storage related, communication related, or related to providing access to another user. Examples of services provided as part of a Djinn include devices, such as printers, displays, and disks; software, such as programs or utilities; information, such as databases and files; and users of the system. [0072]
  • Both users and devices may join a Djinn. When joining a Djinn, the user or device adds zero or more services to the Djinn and may access, subject to security constraints, any one of the services it contains. Thus, devices and users federate into a Djinn to share access to its services. The services of the Djinn appear programmatically as objects of the Java programming environment, which may include other objects, software components written in different programming languages, or hardware devices. A service has an interface defining the operations that can be requested of that service, and the type of the service determines the interfaces that make up that service. [0073]
  • Distributed [0074] system 400 is comprised of computer 402, a computer 404, and a device 406 interconnected by a network 408. Device 406 may be any of a number of devices, such as a printer, fax machine, storage device, computer, or other devices. Network 408 may be a local area network, wide area network, or the Internet. Although only two computers and one device are depicted as comprising distributed system 400, one skilled in the art will appreciate that distributed system 400 may include additional computers or devices.
  • FIG. 5 depicts [0075] computer 402 in greater detail to show a number of the software components of distributed system 400. One skilled in the art will appreciate that computer 404 or device 406 may be similarly configured. Computer 402 includes a memory 502, a secondary storage device 504, a central processing unit (CPU) 506, an input device 508, and a video display 510. Memory 502 includes a lookup service 512, a discovery server 514, and a Java runtime system 516. The Java runtime system 516 includes the Java RMI system 518 and a JVM 520. Secondary storage device 504 includes a Java space 522.
  • As mentioned above, distributed [0076] system 400 is based on the Java programming environment and thus makes use of the Java runtime system 516. The Java runtime system 516 includes the Java API libraries, allowing programs running on top of the Java runtime system to access, in a platform-independent manner, various system functions, including windowing capabilities and networking capabilities of the host operating system. Since the Java API libraries provides a single common API across all operating systems to which the Java runtime system is ported, the programs running on top of a Java runtime system run in a platform-independent manner, regardless of the operating system or hardware configuration of the host platform. The Java runtime system 516 is provided as part of the Java software development kit available from Sun Microsystems, Inc. of Mountain View, Calif.
  • [0077] JVM 520 also facilitates platform independence. JVM 520 acts like an abstract computing machine, receiving instructions from programs in the form of bytecodes and interpreting these bytecodes by dynamically converting them into a form for execution, such as object code, and executing them. RMI 518 facilitates remote method invocation by allowing objects executing on one computer or device to invoke methods of an object on another computer or device. Both RMI and the JVM are also provided as part of the Java software development kit.
  • [0078] Lookup service 512 defines the services that are available for a particular Djinn. That is, there may be more than one Djinn and, consequently, more than one lookup service within distributed system 400. Lookup service 512 contains one object for each service within the Djinn, and each object contains various methods that facilitate access to the corresponding service. Lookup service 512 is described in U.S. patent application entitled “Method and System for Facilitating Access to a Lookup Service,” which was previously incorporated herein by reference.
  • [0079] Discovery server 514 detects when a new device is added to distributed system 400, during a process known as boot and join (or discovery), and when such a new device is detected, the discovery server passes a reference to lookup service 512 to the new device so that the new device may register its services with the lookup service and become a member of the Djinn. After registration, the new device becomes a member of the Djinn, and as a result, it may access all the services contained in lookup service 512. The process of boot and join is described in U.S. patent application entitled “Apparatus and Method for providing Downloadable Code for Use in Communicating with a Device in a Distributed System,” which was previously incorporated herein by reference.
  • A [0080] Java space 522 is an object repository used by programs within distributed system 400 to store objects. Programs use a Java space 522 to store objects persistently as well as to make them accessible to other devices within distributed system 400. Java spaces are described in U.S. patent application Ser. No. 08/971,529, entitled “Database System Employing Polymorphic Entry and Entry Matching,” assigned to a common assignee, and filed on Nov. 17, 1997, which is incorporated herein by reference. One skilled in the art will appreciate that an exemplary distributed system 400 may contain many lookup services, discovery servers, and Java spaces.
  • Data Flow in a Distributed Processing System
  • FIG. 6 is a diagram of an object-oriented distributed [0081] system 600 connecting machines 601, 602, and 603, such as computers or virtual machines executing on one or more computers, or the machines described with reference to FIG. 3. Transmitting machine 601 includes a memory 604 storing objects such as objects 605 and 606, and RMI 607 for performing processing on the objects. To transmit an object over network 600, RMI 607 uses code 609 for converting object 605 into a marshalled object that is transmitted as a byte stream 608 to machine 602. Streams used in the Java programming language, including input and output streams, are known in the art and an explanation, which is incorporated herein by reference, appears in, for example, a text entitled “The Java Tutorial: Object-Oriented Programming for the Internet,” pp. 325-53, by Mary Campione and Kathy Walrath, Addison-Wesley, 1996.
  • Part of this conversion includes adding information so that a receiving [0082] machine 602 can reconstruct the object. When a set of object types is limited and is the same on all machines 601, 602, and 603, a receiving machine typically requires the object's state and a description of its type because the object's code is already present on all network machines. Alternatively, machine 601 uses RMI 607 to provide more flexibility, allowing code to be moved when necessary along with information or the object's state and type. Additionally, a transmitting machine includes in the marshalled object an identification of the type of object transmitted, the data constituting the state of the object, and a network-accessible location in the form of a URL for code that is associated with the object. URLs are known in the art and an explanation, which is incorporated herein by reference, appears in, for example, a text entitled “The Java Tutorial: Object-Oriented Programming for the Internet,” pp. 494-507, by Mary Campione and Kathy Walrath, Addison-Wesley, 1996.
  • When receiving [0083] machine 602 receives byte stream 608, it identifies the type of transmitted object. Machine 602 contains its own RMI 610 and code 611 for processing of objects. If byte stream 608 contains a marshalled object, machine 602 may create a new object 614 using the object type identified in the marshalled object, the state information, and code for the object. Object 614 is a copy of object 605 and is stored in memory 613 of machine 602. If code 612 is not resident or available on machine 602 and the marshalled object does not contain the code, RMI 610 uses the URL from the marshalled object to locate the code and transfer a copy of the code to machine 602. Code 612 is generally only required if the object is unmarshalled. Because the code is in bytecode format and is therefore portable, the receiving machine can load the code into RMI 610 to reconstruct the object. Thus, machine 602 can reconstruct an object of the appropriate type even if that kind of object has not been present on the machine before.
  • [0084] Machine 602 may also convert object 614 into byte stream 615 for transmission to a third machine 603, which contains its own RMI 618 and code 619 for processing objects. RMI 618, using code 620 for the object, converts byte stream 615 into a corresponding object 616, which it stores in memory 617. Object 616 is a copy of object 605. If code 620 for the object is not resident or available, machine 603 requests the code from another machine using the URL, as described above.
  • [0085] Machine 602 may alternatively store the marshalled object as a byte stream without reconstructing the object. It may then transmit the byte stream to machine 603.
  • Marshalled Object
  • A marshalled object is a container for an object that allows that object to be passed as a parameter in RMI call, but postpones conversion of the marshalled object at the receiving machine until a program executing on the receiving machine explicitly requests the object via a call to the marshalled object. A container is an envelope that includes the data and either the code or a reference to the code for the object, and that holds the object for transmission. The serializable object contained in the marshalled object is typically serialized and deserialized when requested with the same semantics as parameters passed in RMI calls. Serialization is a process of converting an in-memory representation of an object into a corresponding self-describing byte stream. Deserialization is a process of converting a self-describing byte stream into the corresponding object. [0086]
  • To convert an object into a marshalled object, the object is placed inside a marshalled object container and when a URL is used to locate code for the object, the URL is added to the container. Thus, when the contained object is retrieved from its marshalled object container, if the code for the object is not available locally, the URL added to the container is used to locate and load code in bytecode format for the object's class. [0087]
  • Table 1 provides an exemplary class definition in the Java programming language for a marshalled object consistent with the present invention. [0088]
    TABLE 1
    package java.rmi;
    public final class MarshalledObject implements java.io.Serializable
    {
    public MarshalledObject (Object obj)
    throws java.io.IOException;
    public Object get ( )
    throws java.io.IOExeception, ClassNotFoundException;
    public int hashCode ( );
    public boolean equals( );
    }
  • A marshalled object may be embodied within an article of manufacture specifying a representation of the object stored in a computer-readable storage medium. [0089]
  • A marshalled object's constructor takes a serializable object (obj) as its single argument and holds the marshalled representation of the object in a byte stream. The marshalled representation of the object preserves the semantics of objects that are passed in RMI calls: each class in the stream is typically annotated with either the object's code or a URL to the code so that when the object is reconstructed by a call to a “get” method, the bytecodes for each class can be located and loaded, and remote objects are replaced with their proxy stubs. The “get” method is a method called by a program to execute a process of unmarshalling, which is reconstruction of an object from a marshalled object using a self-describing byte stream (the marshalled object), and a process to obtain the necessary code for that process. A proxy stub is a reference to a remote object for use in reconstructing an object. [0090]
  • When an instance of the class marshalled object is written to a “java.io.ObjectOutputStream,” the contained object's marshalled form created during construction is written to the stream. Thus, only the byte stream is serialized. [0091]
  • When a marshalled object is read from a “java.io.ObjectInputStream,” the contained object is not deserialized into a new object. Rather, the object remains in its marshalled representation until the marshalled object's get method is called. [0092]
  • The “get” method preferably always reconstructs a new copy of the contained object from its marshalled form. The internal representation is deserialized with the same semantics used for unmarshalling parameters for RMI calls. Thus, the deserialization of the object's representation loads class codes, if not available locally, using the URL annotation embedded in the serialized stream for the object. [0093]
  • As indicated in the class definition for a marshalled object, the hash code of the marshalled representation of an object is defined to be equivalent to the hash code for the object itself. In general, a hash code is used in hash tables to perform fast look-ups of information, which is known in the art. The equals method will return true if the marshalled representation of the objects being compared are equivalent. An equals method verifies reconstruction by determining if a reconstructed object is the same as the original object, and such methods are known in the Java programming language. [0094]
  • Transmission of a Marshalled Object
  • FIG. 7 is a flow diagram of [0095] steps 700 preferably performed in transmitting objects in a distributed system consistent with the present invention. A machine receives a byte stream (step 701), which includes data for the object, information identifying the type of object, and optionally a URL for the code that is associated with the object. The receiving machine determines if the code for the object is resident or available (step 702). If it is available, the machine preferably uses RMI for reconstructing the object from the byte stream and resident code (step 704). If the code is not resident, the machine uses the URL from the byte stream to request the code from another machine located at a network accessible location, and that machine returns a copy of the code (step 703). The object can also be transmitted in the form of a byte stream to another machine (step 705).
  • FIG. 8 is a flow diagram of [0096] steps 800 preferably performed for deferring code loading and construction of objects when transmitting marshalled objects in a distributed system consistent with the present invention. A machine receives a byte stream (step 801), which includes data for the object, information identifying the type of object, and optionally a URL for the code that is associated with the object.
  • The machine determines if the byte stream is a marshalled object (step [0097] 802). If it is not such an object, the machine performs normal processing of the byte stream (step 803). Otherwise, if the received byte stream represents a marshalled object, the machine holds the marshalled object for later use in response to a get method invoked by a process on the receiving machine. If the receiving machine determines that the object is to be transmitted to another machine (step 804), it simply transmits the byte stream without reconstructing the object. If the machine uses the object, it performs reconstruction of the object using its RMI and associated code (step 805). If the reconstruction code for the object is not resident on the machine, it uses a URL to request and obtain the code (step 806), as described above. The machine determines if it needs to transmit the object to another machine (step 807). If the object is destined for another machine, it is transmitted as a byte stream (step 808).
  • Accordingly, a marshalled object provides for more efficient transfer of objects in a distributed system. If an object is needed by a machine, it can be reconstructed, and if the machine does not need to use the object, it can transmit the marshalled object without reconstructing it. [0098]
  • Use of a Marshalled Object in Event Notification
  • A distributed system or network may use marshalled objects in conjunction with registration for notification of events within the system. FIG. 9 is a diagram of a distributed [0099] network 900 illustrating event notification. Network 900 may use the machines described with reference to FIGS. 3, 4, and 5. Network 900 includes a remote event listener 901 having RMI 902 and object 903, a machine 904 having RMI 905 and object 906, and an event generator 907 having RMI 908 and object 909 for providing event notification. Machine 904 may be the same as remote event listener 901, as indicated by the dashed line, or they may be separate machines.
  • [0100] Machine 904, desiring notification of a particular network event, registers with RMI 908 by transmitting a request for event notification including or associated with a marshalled object 912. Event generator 907 stores the marshalled object for possible later transmission. When RMI 908 detects an occurrence of the event, it transmits notification of the event along with the marshalled object 913 to remote event listener 901. Remote event listener 901 may make a call to code server 910 in order to obtain code 911 for reconstructing the marshalled object, which may contain information relating to the event. A code server is an entity and process that has access to code and responds to requests for a particular type or class of object and returns code for that object. A code server may be located within machine 901 or on another machine. Also, the code may be resident on the same platform as the code server or on a separate platform. After registration, remote event listener 901 may provide indications of the particular event when detected.
  • FIG. 10 is a flow chart of a [0101] process 1000 or event notification within a distributed network, such as network 900. A machine sends a registration request including a marshalled object to a remote event generator (step 1001), which stores the marshalled object for possible later transmission (step 1002). The event generator determines if the event occurred (step 1003), and, if it detects such an occurrence, it sends notification of the event including the stored marshalled object to an event listener machine (step 1004). The event generator determines, based on particular criteria or system requirements, if it is to continue providing notification of occurrences of the event (step 1005). If so, it continues to determine if the event occurred. These steps may use, for example, interfaces and class definitions written in the Java programming language shown in Tables 1-5 provided in this specification.
  • Table 2 provides an example of an interface in the Java programming language for implementing a remote event listener. [0102]
    TABLE 2
    public interface RemoteEventListener extends Remote,
    java.util.EventListener
    {
    void notify(RemoteEvent theEvent)
    throws EventUnknownException, RemoteException;
    }
  • In the interface shown in Table 2, the notify method has a single parameter of type “RemoteEvent” that is used during operation to encapsulate the information passed as part of a notification. Table 3 provides an example of a definition for the public part of the “RemoteEvent” class definition. [0103]
    TABLE 3
    public class RemoteEvent extends EventObject
    {
    public RemoteEvent (Object evSource,
    long evIdNo,
    long evSeqNo)
    public Object getSource ( );
    public long getID( );
    public long getSeqNo ( );
    public MarshalledObject getRegistrationObject ( );
    }
  • In the definition shown in Table 3, the abstract state contained in a “RemoteEvent” object includes a reference to the object in which the event occurred, a “long” which identifies the kind of event relative to the object in which the event occurred, and a “long” which indicates the sequence number (“SeqNo”) of this instance of the event kind. The sequence number obtained from the “RemoteEvent” object is an increasing value that may provide an indication concerning the number of occurrences of this event relative to an earlier sequence number. [0104]
  • Table 4 provides an example of an interface in the Java programming language for an event generator. [0105]
    TABLE 4
    public interface EventGenerator extends Remote
    {
    public EventRegistration register (long evId,
    MarshalledObject handback,
    RemoteEventListener toInform,
    long leasePeriod)
    throws EventUnknownException, RemoteException;
    }
  • The register method shown in Table 4 allows registration of interest in the occurrence of an event inside an object. While executing this method, a JVM receives an “evId,” which is a long integer used to identify the class of events; an object that is transmitted back as part of the notification; a reference to a “RemoteEventListener” object; and a long integer indicating the leasing period for the interest registration. If an “evId” is provided to this call that is not recognized by the event generator object, the JVM signals an error. In the Java programming language, a JVM is said to “throw” an “EventUnknownException” to signal that error. The second argument of the register method is a marshalled object that is to be transmitted back as part of the notification generated when an event of the appropriate type occurs. The third argument of the register method is a remote event listener object that receives any notifications of instances of the event kind occurring. This argument may be the object that is registering interest, or it may be another remote event listener such as a third-party event handler or notification “mailbox.” The final argument to the register method is a “long” indicating the requested duration of the registration, referred to as the “lease.”[0106]
  • The return value of the register method is an object of the event registration class definition. This object contains a “long” identifying the kind of event in which interest was registered relative to the object granting the registration, a reference to the object granting the registration, and a lease object containing information concerning the lease period. [0107]
  • Table 5 provides an example of a class definition in the Java programming language for event registration. [0108]
    TABLE 5
    public class EventRegistration implements java.io.Serializable {
    public EventRegistration (long eventNum,
    Remote registerWith,
    Lease eventLease,
    long currentSeqNum);
    public long getEventID ( );
    public Object getEventSource ( );
    public LeasegetLease ( );
    public long currentSeqNum ( );
    }
  • In the class definition shown in Table 5, the “getEventID” method returns the identifier of the event in which interest was registered, which combined with the return value of the “getEventSource” method uniquely identifies the kind of event. This information is provided to third-party repositories to allow them to recognize the event and route it correctly. During operation in a JVM, the “getLease” method returns the lease object for this registration and is used in lease maintenance. The “currentSeqNo” method returns the value of the sequence number on the event kind that was current when the registration was granted, allowing comparison with the sequence number in any subsequent notifications. A “toString” method may be used with this class definition to return a human-readable string containing the information making up the state of the object. [0109]
  • Machines implementing the steps shown in FIGS. 7, 8, and [0110] 10 may include computer processors for performing the functions, as shown in FIGS. 3, 4, and 5. They may include modules or programs configured to cause the processors to perform the above functions. They may also include computer program products stored in a memory. The computer program products may include a computer-readable medium or media having computer-readable code embodied therein for causing the machines to perform functions described above. The media may include a computer data signal embodied in a carrier wave and representing sequences of instructions which, when executed by a processor, cause the processor to securely address a peripheral device at an absolute address by performing the method described in this specification. The media may also include data structures for use in performing the method described in this specification.
  • Although the illustrative embodiments of the systems consistent with the present invention are described with reference to a computer system implementing the Java programming language on the JVM specification, the invention is equally applicable to other computer systems processing code from different programming languages. Specifically, the invention may be implemented with both object-oriented and nonobject-oriented programming systems. In addition, although an embodiment consistent with the present invention has been described as operating in the Java programming environment, one skilled in the art will appreciate that the present invention can be used in other programming environments as well. [0111]
  • While the present invention has been described in connection with an exemplary embodiment, it will be understood that many modifications will be readily apparent to those skilled in the art, and this application is intended to cover any adaptations or variations thereof. For example, different labels or definitions for the marshalled object may be used without departing from the scope of the invention. This invention should be limited only by the claims and equivalents thereof. [0112]

Claims (20)

What is claimed is:
1. A method for transmitting objects in a distributed system comprised of multiple machines, comprising:
specifying an object associated with a request for notification of a particular event within the system;
converting the object into a stream containing a self-describing form of the object; and
providing the stream for selective transmission to a machine where the object is reconstructed by accessing program code identified in the stream upon occurrence of the event.
2. The method of claim 1 wherein the providing includes
storing the stream prior to the selective transmission.
3. The method of claim 1 wherein the converting includes
packaging the object in an unconstructed package including a reference to the program code for reconstructing the object.
4. A method for processing objects in a distributed system comprised of multiple machines, comprising:
receiving at a first machine a stream containing a self-describing form of an object associated with a request for notification of a particular event within the system;
determining whether to send the stream to a second machine; and
selectively sending the stream to the second machine for reconstruction of the object by accessing program code identified in the stream, the first machine providing notification of the event.
5. An apparatus for transmitting objects in a distributed system comprised of multiple machines, comprising:
a module configured to specify an object associated with a request for notification of a particular event within the system;
a module configured to convert the object into a stream containing a self-describing form of the object; and
a module configured to provide the stream for selective transmission to a machine where the object is reconstructed by accessing program code identified in the stream upon occurrence of the event.
6. The apparatus of claim 5 wherein the providing module includes
a module configured to store the stream prior to the selective transmission.
7. The apparatus of claim 5 wherein the converting module includes
a module configured to package the object in an unconstructed package including a reference to the program code for reconstructing the object.
8. An apparatus for processing objects in a distributed system comprised of multiple machines, comprising:
a module configured to receive at a first machine a stream containing a self-describing form of an object associated with a request for notification of a particular event within the system;
a module configured to determine whether to send the stream to a second machine; and
a module configured to selectively send the stream to the second machine for reconstruction of the object by accessing program code identified in the stream, the first machine providing notification of the event.
9. A system for transmitting objects in a distributed system comprised of multiple machines, comprising:
a first machine;
a second machine;
a network connecting the first machine with the second machine; and
an apparatus for transmitting objects in the system, the apparatus including:
a module configured to specify an object associated with a request for notification of a particular event within the system;
a module configured to convert the object into a stream containing a self-describing form of the object; and
a module configured to provide the stream for selective transmission to a machine where the object is reconstructed by accessing program code identified in the stream upon occurrence of the event.
10. The system of claim 9 wherein the providing module includes
a module configured to store the stream prior to the selective transmission.
11. The system of claim 9 wherein the converting module includes
a module configured to package the object in an unconstructed package including a reference to the program code for reconstructing the object.
12. A system for transmitting objects in a distributed system comprised of multiple machines, comprising:
a first machine;
a second machine;
a network connecting the first machine with the second machine; and
an apparatus for transmitting objects in the system, the apparatus including:
a module configured to receive at the first machine a stream containing a self-describing form of an object associated with a request for notification of a particular event within the system;
a module configured to determine whether to send the stream to the second machine; and
a module configured to selectively send the stream to the second machine for reconstruction of the object by accessing program code identified in the stream, the first machine providing notification of the event.
13. A computer program product, comprising:
a computer-readable medium containing instructions for controlling a computer system to perform a method, the method including:
specifying an object associated with a request for notification of a particular event within the system;
converting the object into a stream containing a self-describing form of the object; and
providing the stream for selective transmission to a machine where the object is reconstructed by accessing program code identified in the stream upon occurrence of the event.
14. The computer program product of claim 13 wherein the providing includes
storing the stream prior to the selective transmission.
15. The computer program product of claim 13 wherein the converting includes
packaging the object in an unconstructed package including a reference to the program code for reconstructing the object.
16. A computer program product, comprising:
a computer-readable medium containing instructions for controlling a computer system to perform a method, the method including:
receiving at a first machine a stream containing a self-describing form of an object associated with a request for notification of a particular event within the system;
determining whether to send the stream to a second machine; and
selectively sending the stream to the second machine for reconstruction of the object by accessing program code identified in the stream, the first machine providing notification of the event.
17. An article of manufacture specifying a representation of an object stored in a computer-readable storage medium and capable of electronic transmission between machines in a distributed system, the article of manufacture comprising:
a first object comprising a self-describing stream stored in a computer-readable storage medium, the first object being associated with a second object specifying a request for notification of an event in the system, the first object having a property indicating that the first object is to be maintained as the stream when the first object is transmitted between machines in the system unless occurrence of the event is detected.
18. The article of manufacture of claim 17 wherein the stream includes computer-readable instructions for use in reconstructing the second object.
19. The article of manufacture of claim 17 wherein the stream includes a location of computer-readable instructions for use in reconstructing the second object.
20. An apparatus for transmitting objects in a distributed system comprised of multiple machines, comprising:
means for specifying an object associated with a request for notification of a particular event within the system;
means for converting the object into a stream containing a self-describing form of the object; and
means for providing the stream for selective transmission to a machine where the object is reconstructed by accessing program code identified in the stream upon occurrence of the event.
US09/891,178 1997-10-15 2001-08-03 Deferred reconstruction of objects and remote loading for event notification in a distributed system Abandoned US20020091874A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US09/891,178 US20020091874A1 (en) 1997-10-15 2001-08-03 Deferred reconstruction of objects and remote loading for event notification in a distributed system

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US08/950,756 US6253256B1 (en) 1997-10-15 1997-10-15 Deferred reconstruction of objects and remote loading in a distributed system
US09/044,919 US6272559B1 (en) 1997-10-15 1998-03-20 Deferred reconstruction of objects and remote loading for event notification in a distributed system
US09/891,178 US20020091874A1 (en) 1997-10-15 2001-08-03 Deferred reconstruction of objects and remote loading for event notification in a distributed system

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/044,919 Continuation US6272559B1 (en) 1996-04-23 1998-03-20 Deferred reconstruction of objects and remote loading for event notification in a distributed system

Publications (1)

Publication Number Publication Date
US20020091874A1 true US20020091874A1 (en) 2002-07-11

Family

ID=26722154

Family Applications (2)

Application Number Title Priority Date Filing Date
US09/044,919 Expired - Lifetime US6272559B1 (en) 1996-04-23 1998-03-20 Deferred reconstruction of objects and remote loading for event notification in a distributed system
US09/891,178 Abandoned US20020091874A1 (en) 1997-10-15 2001-08-03 Deferred reconstruction of objects and remote loading for event notification in a distributed system

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/044,919 Expired - Lifetime US6272559B1 (en) 1996-04-23 1998-03-20 Deferred reconstruction of objects and remote loading for event notification in a distributed system

Country Status (1)

Country Link
US (2) US6272559B1 (en)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050143907A1 (en) * 2003-12-13 2005-06-30 Kim Jeong S. Driver agent device for supporting remote device driver development environment in embedded system and operation method thereof
US7143160B2 (en) * 2001-03-09 2006-11-28 Fujitsu Limited Event-driven information display system and event-driven information display method
WO2005122720A3 (en) * 2004-06-10 2007-03-22 Cisco Tech Inc A generic framework for deploying ems provisioning services
US20080182576A1 (en) * 2007-01-22 2008-07-31 Qualcomm Incorporated Message ordering for network based mobility management systems
US20080196006A1 (en) * 2007-02-06 2008-08-14 John Bates Event-based process configuration
US20090254923A1 (en) * 2005-01-14 2009-10-08 International Business Machines Corporation Mechanism that Provides More Efficient Event Handler Processing
US7653681B2 (en) 2005-01-14 2010-01-26 International Business Machines Corporation Software architecture for managing a system of heterogenous network processors and for developing portable network processor applications
US20110167431A1 (en) * 2010-01-05 2011-07-07 Seiko Epson Corporation Control of apparatus incorporating computer
US9436635B1 (en) * 2011-08-30 2016-09-06 Emc Corporation Leases in a heterogenous data environment

Families Citing this family (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6185611B1 (en) 1998-03-20 2001-02-06 Sun Microsystem, Inc. Dynamic lookup service in a distributed system
US6832223B1 (en) 1996-04-23 2004-12-14 Sun Microsystems, Inc. Method and system for facilitating access to a lookup service
US6393497B1 (en) 1998-03-20 2002-05-21 Sun Microsystems, Inc. Downloadable smart proxies for performing processing associated with a remote procedure call in a distributed system
US6466947B2 (en) * 1998-03-20 2002-10-15 Sun Microsystems, Inc. Apparatus and method for dynamically verifying information in a distributed system
US6421704B1 (en) * 1998-03-20 2002-07-16 Sun Microsystems, Inc. Method, apparatus, and product for leasing of group membership in a distributed system
US6728737B2 (en) 1996-10-11 2004-04-27 Sun Microsystems, Inc. Method and system for leasing storage
US5832529A (en) 1996-10-11 1998-11-03 Sun Microsystems, Inc. Methods, apparatus, and product for distributed garbage collection
US6704803B2 (en) 1998-01-26 2004-03-09 International Business Machines Corporation Method and system for distributing data events over an information bus
US6704804B1 (en) 1998-01-26 2004-03-09 International Business Machines Corporation Method and system for communicating information among interactive applications
AU2680399A (en) 1998-02-26 1999-09-15 Sun Microsystems, Inc. Apparatus and method for dynamically verifying information in a distributed system
CN1298514A (en) 1998-02-26 2001-06-06 太阳微系统公司 Method and system for deterministic hashes to identify remote method
US20020046228A1 (en) * 1998-03-20 2002-04-18 Sun Microsystems, Inc. Method and system for facilitating access to a lookup service
US6385661B1 (en) * 1998-10-19 2002-05-07 Recursion Software, Inc. System and method for dynamic generation of remote proxies
US6947965B2 (en) * 1999-11-30 2005-09-20 Recursion Software, Inc. System and method for communications in a distributed computing environment
US6625797B1 (en) * 2000-02-10 2003-09-23 Xilinx, Inc. Means and method for compiling high level software languages into algorithmically equivalent hardware representations
US20040015840A1 (en) * 2001-04-19 2004-01-22 Avaya, Inc. Mechanism for converting between JAVA classes and XML
US7756969B1 (en) 2001-09-07 2010-07-13 Oracle America, Inc. Dynamic provisioning of identification services in a distributed system
US20030051029A1 (en) * 2001-09-07 2003-03-13 Reedy Dennis G. Dynamic provisioning of sevice components in a distributed system
US7660887B2 (en) 2001-09-07 2010-02-09 Sun Microsystems, Inc. Systems and methods for providing dynamic quality of service for a distributed system
US7051105B2 (en) * 2002-08-08 2006-05-23 International Business Machines Corporation System and method for distributing management events to external processes
US20040122892A1 (en) * 2002-12-24 2004-06-24 Brittenham Peter J. Method, apparatus, and computer-program product for event service declaration, registration, and notification
US7478399B2 (en) 2003-04-21 2009-01-13 International Business Machines Corporation Method, system and program product for transferring program code between computer processes
US7689986B2 (en) * 2003-10-21 2010-03-30 Gemstone Systems, Inc. Shared listeners in shared object space
US7792874B1 (en) 2004-01-30 2010-09-07 Oracle America, Inc. Dynamic provisioning for filtering and consolidating events
KR101120788B1 (en) * 2004-04-30 2012-03-23 마이크로소프트 코포레이션 Rules framework for definition and execution of end-user rules logic
US7587721B2 (en) * 2004-05-20 2009-09-08 Sap Ag Sharing objects in runtime systems
US7404108B2 (en) * 2004-08-06 2008-07-22 International Business Machines Corporation Notification method and apparatus in a data processing system
US7565663B2 (en) * 2005-02-28 2009-07-21 Microsoft Corporation Automated data organization
US20060195411A1 (en) * 2005-02-28 2006-08-31 Microsoft Corporation End user data activation
US8239877B2 (en) * 2007-08-28 2012-08-07 International Business Machines Corporation Pre-population of meta data cache for resolution of data marshaling issues
US20090204956A1 (en) * 2008-02-08 2009-08-13 International Business Machines Corporation Multiple-mode software license enforcement
US9660993B2 (en) * 2012-10-25 2017-05-23 Facebook, Inc. Event reporting and handling
US10379846B1 (en) * 2018-01-25 2019-08-13 Walmart Apollo, Llc Systems and methods for real time version control for integrating updated web-based components with a native application
US10296309B1 (en) * 2018-01-25 2019-05-21 Walmart Apollo, Llc Systems and methods for automatic API generation for bi-directional communication between native and web-based components of a mobile application
US10296298B1 (en) * 2018-01-25 2019-05-21 Walmart Apollo, Llc Systems and methods for cross platform information exchange mechanism for integrating web-based components with a native application

Citations (97)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3449669A (en) * 1965-03-05 1969-06-10 Aga Ab Frequency control circuit transforming phase angle into frequency
US4567359A (en) * 1984-05-24 1986-01-28 Lockwood Lawrence B Automatic information, goods and services dispensing system
US4800488A (en) * 1985-11-12 1989-01-24 American Telephone And Telegraph Company, At&T Bell Laboratories Method of propagating resource information in a computer network
US4819233A (en) * 1987-04-08 1989-04-04 Westinghouse Electric Corp. Verification of computer software
US4992940A (en) * 1989-03-13 1991-02-12 H-Renee, Incorporated System and method for automated selection of equipment for purchase through input of user desired specifications
US5307490A (en) * 1992-08-28 1994-04-26 Tandem Computers, Inc. Method and system for implementing remote procedure calls in a distributed computer system
US5319542A (en) * 1990-09-27 1994-06-07 International Business Machines Corporation System for ordering items using an electronic catalogue
US5327559A (en) * 1990-10-23 1994-07-05 International Business Machines Corporation Remote and batch processing in an object oriented programming system
US5339430A (en) * 1992-07-01 1994-08-16 Telefonaktiebolaget L M Ericsson System for dynamic run-time binding of software modules in a computer system
US5339477A (en) * 1991-01-07 1994-08-23 Ron Warner Associates Apparatus for removing coatings from fingernails
US5341477A (en) * 1989-02-24 1994-08-23 Digital Equipment Corporation Broker for computer network server selection
US5446901A (en) * 1993-06-30 1995-08-29 Digital Equipment Corporation Fault tolerant distributed garbage collection system and method for collecting network objects
US5491791A (en) * 1995-01-13 1996-02-13 International Business Machines Corporation System and method for remote workstation monitoring within a distributed computing environment
US5511196A (en) * 1992-11-17 1996-04-23 International Business Machines Corporation Method and system in a data processing system for the enhancement of relationships between reference objects in an object oriented environment and a data object outside an object oriented environment
US5544040A (en) * 1991-08-09 1996-08-06 Gerbaulet; Jean-Pierre System for management of common purchase operations for goods and services
US5548724A (en) * 1993-03-22 1996-08-20 Hitachi, Ltd. File server system and file access control method of the same
US5548726A (en) * 1993-12-17 1996-08-20 Taligeni, Inc. System for activating new service in client server network by reconfiguring the multilayer network protocol stack dynamically within the server node
US5555427A (en) * 1989-12-26 1996-09-10 Fujitsu Limited Distributed processing in a system of computers at terminals connected by a communication network
US5592375A (en) * 1994-03-11 1997-01-07 Eagleview, Inc. Computer-assisted system for interactively brokering goods or services between buyers and sellers
US5594921A (en) * 1993-12-17 1997-01-14 Object Technology Licensing Corp. Authentication of users with dynamically configurable protocol stack
US5644720A (en) * 1995-07-31 1997-07-01 West Publishing Company Interprocess communications interface for managing transaction requests
US5664110A (en) * 1994-12-08 1997-09-02 Highpoint Systems, Inc. Remote ordering system
US5664111A (en) * 1994-02-16 1997-09-02 Honicorp, Inc. Computerized, multimedia, network, real time, interactive marketing and transactional system
US5706502A (en) * 1996-03-25 1998-01-06 Sun Microsystems, Inc. Internet-enabled portfolio manager system and method
US5710887A (en) * 1995-08-29 1998-01-20 Broadvision Computer system and method for electronic commerce
US5715314A (en) * 1994-10-24 1998-02-03 Open Market, Inc. Network sales system
US5721825A (en) * 1996-03-15 1998-02-24 Netvision, Inc. System and method for global event notification and delivery in a distributed computing environment
US5721832A (en) * 1995-05-12 1998-02-24 Regal Greetings & Gifts Inc. Method and apparatus for an interactive computerized catalog system
US5724540A (en) * 1988-03-28 1998-03-03 Hitachi, Ltd. Memory system having a column address counter and a page address counter
US5727048A (en) * 1995-03-01 1998-03-10 Fujitsu Limited Multimedia communication system with a multimedia server to terminals via a public network
US5729594A (en) * 1996-06-07 1998-03-17 Klingman; Edwin E. On-line secured financial transaction system through electronic media
US5734706A (en) * 1995-07-27 1998-03-31 Windsor; Victoria Brein Caller identification and data retrieval system
US5732706A (en) * 1996-03-22 1998-03-31 Lockheed Martin Ir Imaging Systems, Inc. Ultrasonic array with attenuating electrical interconnects
US5737706A (en) * 1995-08-03 1998-04-07 Bell Atlantic Network Services, Inc. Power system supporting CDPD operation
US5742768A (en) * 1996-07-16 1998-04-21 Silicon Graphics, Inc. System and method for providing and displaying a web page having an embedded menu
US5745755A (en) * 1994-01-05 1998-04-28 Covey; Peter J. Method for creating and maintaining a database for a dynamic enterprise
US5745703A (en) * 1995-07-18 1998-04-28 Nec Research Institute, Inc. Transmission of higher-order objects across a network of heterogeneous machines
US5748897A (en) * 1996-07-02 1998-05-05 Sun Microsystems, Inc. Apparatus and method for operating an aggregation of server computers using a dual-role proxy server computer
US5758328A (en) * 1996-02-22 1998-05-26 Giovannoli; Joseph Computerized quotation system and method
US5758077A (en) * 1996-08-02 1998-05-26 Hewlett-Packard Company Service-centric monitoring system and method for monitoring of distributed services in a computing network
US5764982A (en) * 1992-10-30 1998-06-09 International Business Machines Corporation Peer-to-peer communication interface
US5774729A (en) * 1991-12-19 1998-06-30 International Business Machines Corporation Event handling in a high level programming language environment
US5778187A (en) * 1996-05-09 1998-07-07 Netcast Communications Corp. Multicasting method and apparatus
US5778179A (en) * 1991-12-26 1998-07-07 Kabushiki Kaisha Toshiba System for flexible distributed processing and transaction processing suitable for nested transaction
US5790677A (en) * 1995-06-29 1998-08-04 Microsoft Corporation System and method for secure electronic commerce transactions
US5794207A (en) * 1996-09-04 1998-08-11 Walker Asset Management Limited Partnership Method and apparatus for a cryptographically assisted commercial network system designed to facilitate buyer-driven conditional purchase offers
US5799173A (en) * 1994-07-25 1998-08-25 International Business Machines Corporation Dynamic workload balancing
US5872973A (en) * 1995-10-26 1999-02-16 Viewsoft, Inc. Method for managing dynamic relations between objects in dynamic object-oriented languages
US5887172A (en) * 1996-01-10 1999-03-23 Sun Microsystems, Inc. Remote procedure call system and method for RPC mechanism independent client and server interfaces interoperable with any of a plurality of remote procedure call backends
US5889988A (en) * 1995-01-03 1999-03-30 Intel Corporation Debugger for debugging tasks in an operating system virtual device driver
US5889951A (en) * 1996-05-13 1999-03-30 Viewpoint Corporation Systems, methods, and computer program products for accessing, leasing, relocating, constructing and modifying internet sites within a multi-dimensional virtual reality environment
US5905868A (en) * 1997-07-22 1999-05-18 Ncr Corporation Client/server distribution of performance monitoring data
US5915112A (en) * 1996-01-02 1999-06-22 International Business Machines Corporation Remote procedure interface with support for multiple versions
US5925108A (en) * 1995-11-03 1999-07-20 Novell, Inc. Event notification in a computer system
US5940827A (en) * 1995-03-31 1999-08-17 Sun Microsystems, Inc. Methods and apparatus for managing a database in a distributed operating environment
US5944793A (en) * 1996-11-21 1999-08-31 International Business Machines Corporation Computerized resource name resolution mechanism
US6014686A (en) * 1996-06-21 2000-01-11 Telcordia Technologies, Inc. Apparatus and methods for highly available directory services in the distributed computing environment
US6016496A (en) * 1997-11-20 2000-01-18 International Business Machines Corporation Method and apparatus for an object-oriented object for retrieving information from local and remote databases
US6018619A (en) * 1996-05-24 2000-01-25 Microsoft Corporation Method, system and apparatus for client-side usage tracking of information server systems
US6028414A (en) * 1997-01-29 2000-02-22 H Power Enterprises Of Canada Inc. Fuel cell stand-by energy supply system
US6031977A (en) * 1993-12-17 2000-02-29 Object Technology Licensing Corp. Object-oriented distributed communications directory service
US6041351A (en) * 1997-04-17 2000-03-21 Newmoon.Com Network traffic by instruction packet size reduction
US6061699A (en) * 1997-11-03 2000-05-09 International Business Machines Corporation Method and computer program product for extracting translatable material from browser program function codes using variables for displaying MRI
US6085030A (en) * 1997-05-02 2000-07-04 Novell, Inc. Network component server
US6092194A (en) * 1996-11-08 2000-07-18 Finjan Software, Ltd. System and method for protecting a computer and a network from hostile downloadables
US6093216A (en) * 1998-05-29 2000-07-25 Intel Corporation Method of run-time tracking of object references in Java programs
US6101528A (en) * 1996-03-27 2000-08-08 Intel Corporation Method and apparatus for discovering server applications by a client application in a network of computer systems
US6104716A (en) * 1997-03-28 2000-08-15 International Business Machines Corporation Method and apparatus for lightweight secure communication tunneling over the internet
US6189046B1 (en) * 1997-03-27 2001-02-13 Hewlett-Packard Company Mechanism and method for merging cached location information in a distributed object environment
US6212578B1 (en) * 1996-09-09 2001-04-03 Oracle Corporation Method and apparatus for managing dependencies in a distributed computing environment for ensuring the safety of remote procedure calls
US6216158B1 (en) * 1999-01-25 2001-04-10 3Com Corporation System and method using a palm sized computer to control network devices
US6243716B1 (en) * 1996-10-11 2001-06-05 Sun Microsystems, Inc. Methods and systems for distributed failure detection and recovery using leasing
US6243814B1 (en) * 1995-11-02 2001-06-05 Sun Microsystem, Inc. Method and apparatus for reliable disk fencing in a multicomputer system
US6263379B1 (en) * 1992-07-06 2001-07-17 Microsoft Corporation Method and system for referring to and binding to objects using identifier objects
US6269401B1 (en) * 1998-08-28 2001-07-31 3Com Corporation Integrated computer system and network performance monitoring
US20010011350A1 (en) * 1996-07-03 2001-08-02 Mahboud Zabetian Apparatus and method for electronic document certification and verification
US6282581B1 (en) * 1997-03-27 2001-08-28 Hewlett-Packard Company Mechanism for resource allocation and for dispatching incoming calls in a distributed object environment
US6343308B1 (en) * 1997-08-14 2002-01-29 International Business Machines Corporation Systems, methods and computer programs for mixing different versions of Java classes
US6351735B1 (en) * 1989-05-01 2002-02-26 Catalina Marketing International, Inc. Check transaction processing, database building and marketing method and system utilizing automatic check reading
US6363409B1 (en) * 1995-04-24 2002-03-26 Microsoft Corporation Automatic client/server translation and execution of non-native applications
US6378001B1 (en) * 1997-06-18 2002-04-23 International Business Machines Corp. Collaborative framework with shared objects
US6385643B1 (en) * 1998-11-05 2002-05-07 Bea Systems, Inc. Clustered enterprise Java™ having a message passing kernel in a distributed processing system
US20020059212A1 (en) * 2000-10-23 2002-05-16 Nec Corporation Stub search loading system and method, server apparatus, client apparatus, and computer-readable recording medium
US20020073019A1 (en) * 1989-05-01 2002-06-13 David W. Deaton System, method, and database for processing transactions
US6408342B1 (en) * 1997-03-28 2002-06-18 Keith E. Moore Communications framework for supporting multiple simultaneous communications protocols in a distributed object environment
US6418468B1 (en) * 1998-12-03 2002-07-09 Cisco Technology, Inc. Automatically verifying the feasibility of network management policies
US20020111814A1 (en) * 2000-12-12 2002-08-15 Barnett Janet A. Network dynamic service availability
US20030005132A1 (en) * 2001-05-16 2003-01-02 Nortel Networks Limited Distributed service creation and distribution
US6505248B1 (en) * 1999-03-24 2003-01-07 Gte Data Services Incorporated Method and system for monitoring and dynamically reporting a status of a remote server
US20030084204A1 (en) * 1996-04-23 2003-05-01 Ann M. Wollrath System and method for facilitating dynamic loading of "stub"information to enable a program operating in one address space to invoke processing of a remote method or procedure in another address space
US6564174B1 (en) * 1999-09-29 2003-05-13 Bmc Software, Inc. Enterprise management system and method which indicates chaotic behavior in system resource usage for more accurate modeling and prediction
US6578074B1 (en) * 1999-06-25 2003-06-10 Mediaone Group, Inc. Provisioning server enhancement
US6603772B1 (en) * 1999-03-31 2003-08-05 Cisco Technology, Inc. Multicast routing with multicast virtual output queues and shortest queue first allocation
US6604127B2 (en) * 1998-03-20 2003-08-05 Brian T. Murphy Dynamic lookup service in distributed system
US6604140B1 (en) * 1999-03-31 2003-08-05 International Business Machines Corporation Service framework for computing devices
US6704803B2 (en) * 1998-01-26 2004-03-09 International Business Machines Corporation Method and system for distributing data events over an information bus
US6757729B1 (en) * 1996-10-07 2004-06-29 International Business Machines Corporation Virtual environment manager for network computers

Family Cites Families (100)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4491946A (en) 1981-03-09 1985-01-01 Gould Inc. Multi-station token pass communication system
AU556499B2 (en) 1981-05-22 1986-11-06 Data General Corporation Data processing system
JPH0640302B2 (en) 1984-01-30 1994-05-25 株式会社日立製作所 Schematic / source program automatic generation method
US4823122A (en) 1984-06-01 1989-04-18 Digital Equipment Corporation Local area network for digital data processing system
US4809160A (en) 1985-10-28 1989-02-28 Hewlett-Packard Company Privilege level checking instruction for implementing a secure hierarchical computer system
US4713806A (en) 1986-03-14 1987-12-15 American Telephone And Telegraph Company, At&T Bell Laboratories Communication system control arrangement
US4939638A (en) 1988-02-23 1990-07-03 Stellar Computer Inc. Time sliced vector processing
US5287511A (en) 1988-07-11 1994-02-15 Star Semiconductor Corporation Architectures and methods for dividing processing tasks into tasks for a programmable real time signal processor and tasks for a decision making microprocessor interfacing therewith
US4979105A (en) 1988-07-19 1990-12-18 International Business Machines Method and apparatus for automatic recovery from excessive spin loops in an N-way multiprocessing system
US5133075A (en) 1988-12-19 1992-07-21 Hewlett-Packard Company Method of monitoring changes in attribute values of object in an object-oriented database
US5109486A (en) 1989-01-06 1992-04-28 Motorola, Inc. Distributed computer system with network and resource status monitoring
US5088036A (en) 1989-01-17 1992-02-11 Digital Equipment Corporation Real time, concurrent garbage collection system and method
ATE151183T1 (en) 1989-02-24 1997-04-15 Digital Equipment Corp BROKER FOR SELECTING COMPUTER NETWORK SERVERS
US5297283A (en) 1989-06-29 1994-03-22 Digital Equipment Corporation Object transferring system and method in an object based computer operating system
US5551035A (en) * 1989-06-30 1996-08-27 Lucent Technologies Inc. Method and apparatus for inter-object communication in an object-oriented program controlled system
US5557798A (en) 1989-07-27 1996-09-17 Tibco, Inc. Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processes
US5257369A (en) 1990-10-22 1993-10-26 Skeen Marion D Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processes
US5187787B1 (en) 1989-07-27 1996-05-07 Teknekron Software Systems Inc Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processes
US5218699A (en) 1989-08-24 1993-06-08 International Business Machines Corporation Remote procedure calls in heterogeneous systems
GB2242293A (en) 1990-01-05 1991-09-25 Apple Computer Apparatus and method for dynamic linking of computer software components
AU628753B2 (en) 1990-08-14 1992-09-17 Digital Equipment Corporation Method and apparatus for implementing server functions in a distributed heterogeneous environment
AU639802B2 (en) 1990-08-14 1993-08-05 Oracle International Corporation Methods and apparatus for providing dynamic invocation of applications in a distributed heterogeneous environment
US5446897A (en) 1990-08-31 1995-08-29 International Business Machines Corporation Automated address discovery method and apparatus for local area networks
ATE194238T1 (en) 1990-09-17 2000-07-15 Cabletron Systems Inc SYSTEM AND METHOD FOR MODELING A COMPUTER NETWORK
JPH0799497B2 (en) 1990-12-14 1995-10-25 インターナショナル・ビジネス・マシーンズ・コーポレイション Device and method for controlling the use of software
EP0501610B1 (en) 1991-02-25 1999-03-17 Hewlett-Packard Company Object oriented distributed computing system
EP0501613A3 (en) 1991-02-28 1993-09-01 Hewlett-Packard Company Heterogeneous software configuration management apparatus
US5293614A (en) 1991-04-08 1994-03-08 Texas Instruments Incorporated System and method for hard real-time garbage collection requiring a write barrier but no read barrier
US5481721A (en) 1991-07-17 1996-01-02 Next Computer, Inc. Method for providing automatic and dynamic translation of object oriented programming language-based message passing into operation system message passing using proxy objects
DE4131380A1 (en) 1991-09-20 1993-03-25 Siemens Ag METHOD FOR ADAPTING AN OBJECT-ORIENTED APPLICATION
US5826017A (en) 1992-02-10 1998-10-20 Lucent Technologies Apparatus and method for communicating data between elements of a distributed system using a general protocol
US5390328A (en) 1992-03-30 1995-02-14 International Business Machines Corporation Data processing system and method for providing notification in a central processor of state changes for shared data structure on external storage
US5553305A (en) 1992-04-14 1996-09-03 International Business Machines Corporation System for synchronizing execution by a processing element of threads within a process using a state indicator
US5353343A (en) 1992-04-30 1994-10-04 Rockwell International Corporation Telephonic switching system with a user controlled data memory access system and method
US5412717A (en) 1992-05-15 1995-05-02 Fischer; Addison M. Computer system security method and apparatus having program authorization information data structures
JP2524472B2 (en) 1992-09-21 1996-08-14 インターナショナル・ビジネス・マシーンズ・コーポレイション How to train a telephone line based speech recognition system
US5423042A (en) 1992-10-23 1995-06-06 International Business Machines Corporation Remote procedure execution
US5561785A (en) 1992-10-29 1996-10-01 International Business Machines Corporation System for allocating and returning storage and collecting garbage using subpool of available blocks
EP0669020B1 (en) 1992-11-13 1997-04-02 Microsoft Corporation Methods for marshalling interface pointers for remote procedure calls
US5515536A (en) 1992-11-13 1996-05-07 Microsoft Corporation Method and system for invoking methods of an object through a dispatching interface
US5386568A (en) 1992-12-01 1995-01-31 Yamaha Corporation Apparatus and method for linking software modules
EP0602263A1 (en) 1992-12-15 1994-06-22 International Business Machines Corporation User interface program generator
US5560003A (en) 1992-12-21 1996-09-24 Iowa State University Research Foundation, Inc. System and hardware module for incremental real time garbage collection and memory management
DE69429686T2 (en) 1993-02-25 2003-04-30 Sun Microsystems Inc Transaction management in an object-oriented system
US5832593A (en) 1993-04-14 1998-11-10 Minnesota Mining And Manufacturing Company Splice head for insulated telecommunication wires
CA2121612A1 (en) 1993-05-21 1994-11-22 Chung-Hwa Herman Rao Methods and apparatus for making and using distributed applications
US5603031A (en) 1993-07-08 1997-02-11 General Magic, Inc. System and method for distributed computation based upon the movement, execution, and interaction of processes in a network
DK0635792T3 (en) 1993-07-16 2003-10-20 Siemens Ag Method for coordinating parallel access for multiple resource configuration processors
US5844553A (en) 1993-08-30 1998-12-01 Hewlett-Packard Company Mechanism to control and use window events among applications in concurrent computing
US5617537A (en) 1993-10-05 1997-04-01 Nippon Telegraph And Telephone Corporation Message passing system for distributed shared memory multiprocessor system and message passing method using the same
CA2118169A1 (en) 1993-10-27 1995-04-28 Michael R.C. Seaman Event architecture for system management in an operating system
US5455952A (en) 1993-11-03 1995-10-03 Cardinal Vision, Inc. Method of computing based on networks of dependent objects
US5742848A (en) 1993-11-16 1998-04-21 Microsoft Corp. System for passing messages between source object and target object utilizing generic code in source object to invoke any member function of target object by executing the same instructions
US5581704A (en) 1993-12-06 1996-12-03 Panasonic Technologies, Inc. System for maintaining data coherency in cache memory by periodically broadcasting invalidation reports from server to client
US5675796A (en) 1994-04-08 1997-10-07 Microsoft Corporation Concurrency management component for use by a computer program during the transfer of a message
US5680617A (en) 1994-05-16 1997-10-21 Apple Computer, Inc. Computer-human interface which provides for user customization of object behavior
DE69533148T2 (en) 1994-05-26 2005-08-25 Sun Microsystems, Inc., Santa Clara Method and apparatus for creating and using short operation identifiers in object-oriented systems
US5655148A (en) 1994-05-27 1997-08-05 Microsoft Corporation Method for automatically configuring devices including a network adapter without manual intervention and without prior configuration information
US5680573A (en) 1994-07-12 1997-10-21 Sybase, Inc. Method of buffering data objects in a database
US5778228A (en) 1994-08-16 1998-07-07 International Business Machines Corporation Method and system for transferring remote procedure calls and responses over a network
US5555367A (en) 1994-09-30 1996-09-10 General Electric Company Method and system for generating computer programs for queries formed by manipulating object-oriented diagrams
JP4058118B2 (en) 1994-11-15 2008-03-05 株式会社日立製作所 Program generation system and method
US5577231A (en) 1994-12-06 1996-11-19 International Business Machines Corporation Storage access authorization controls in a computer system using dynamic translation of large addresses
US5553282A (en) 1994-12-09 1996-09-03 Taligent, Inc. Software project history database and method of operation
DE69521977T2 (en) 1994-12-13 2002-04-04 Ibm Process and system for secure program distribution
US5872928A (en) 1995-02-24 1999-02-16 Cabletron Systems, Inc. Method and apparatus for defining and enforcing policies for configuration management in communications networks
US5628005A (en) 1995-06-07 1997-05-06 Microsoft Corporation System and method for providing opportunistic file access in a network environment
US5761656A (en) * 1995-06-26 1998-06-02 Netdynamics, Inc. Interaction between databases and graphical user interfaces
US5774551A (en) 1995-08-07 1998-06-30 Sun Microsystems, Inc. Pluggable account management interface with unified login and logout and multiple user authentication services
JP2964926B2 (en) 1995-08-29 1999-10-18 富士ゼロックス株式会社 Database management apparatus and method
US5671225A (en) 1995-09-01 1997-09-23 Digital Equipment Corporation Distributed interactive multimedia service system
US5737607A (en) * 1995-09-28 1998-04-07 Sun Microsystems, Inc. Method and apparatus for allowing generic stubs to marshal and unmarshal data in object reference specific data formats
US5864862A (en) 1996-09-30 1999-01-26 Telefonaktiebolaget Lm Ericsson (Publ) System and method for creating reusable components in an object-oriented programming environment
US5860153A (en) 1995-11-22 1999-01-12 Sun Microsystems, Inc. Memory efficient directory coherency maintenance
US6003763A (en) 1995-12-29 1999-12-21 Visa International Service Method and apparatus for recording magnetic information on traveler's checks
US5745695A (en) 1996-01-16 1998-04-28 Motorola Inc. Radio system with suspension of packet data service during non-data service connection
US5754849A (en) * 1996-01-30 1998-05-19 Wayfarer Communications, Inc. Self-describing object providing dynamic manipulation of heterogeneous data values and semantic identity between memory and transmission representations
US5946485A (en) 1996-02-09 1999-08-31 Intervoice Limited Partnership Enhanced graphical development environment for controlling program flow
US5845129A (en) 1996-03-22 1998-12-01 Philips Electronics North America Corporation Protection domains in a single address space
US5815709A (en) 1996-04-23 1998-09-29 San Microsystems, Inc. System and method for generating identifiers for uniquely identifying object types for objects used in processing of object-oriented programs and the like
US5778368A (en) 1996-05-03 1998-07-07 Telogy Networks, Inc. Real-time embedded software respository with attribute searching apparatus and method
US5835737A (en) 1996-05-10 1998-11-10 Apple Computer, Inc. Method and apparatus for arbitrating access to selected computer system devices
US5813013A (en) 1996-06-06 1998-09-22 Microsoft Corporation Representing recurring events
JP3488019B2 (en) 1996-06-17 2004-01-19 株式会社山武 How to reuse parts of configuration tool for control design
US5768532A (en) 1996-06-17 1998-06-16 International Business Machines Corporation Method and distributed database file system for implementing self-describing distributed file objects
US5727145A (en) 1996-06-26 1998-03-10 Sun Microsystems, Inc. Mechanism for locating objects in a secure fashion
US5809507A (en) 1996-07-01 1998-09-15 Sun Microsystems, Inc. Method and apparatus for storing persistent objects on a distributed object network using a marshaling framework
US5860004A (en) 1996-07-03 1999-01-12 Sun Microsystems, Inc. Code generator for applications in distributed object systems
US5757925A (en) 1996-07-23 1998-05-26 Faybishenko; Yaroslav Secure platform independent cross-platform remote execution computer system and method
US5875335A (en) * 1996-09-30 1999-02-23 Apple Computer, Inc. Parameter marshaling techniques for dynamic object-oriented programming languages
US5787425A (en) 1996-10-01 1998-07-28 International Business Machines Corporation Object-oriented data mining framework mechanism
US5892904A (en) 1996-12-06 1999-04-06 Microsoft Corporation Code certification for network transmission
US5787431A (en) 1996-12-16 1998-07-28 Borland International, Inc. Database development system with methods for java-string reference lookups of column names
US5815149A (en) 1997-02-19 1998-09-29 Unisys Corp. Method for generating code for modifying existing event routines for controls on a form
US5935249A (en) 1997-02-26 1999-08-10 Sun Microsystems, Inc. Mechanism for embedding network based control systems in a local network interface device
US5864866A (en) 1997-03-26 1999-01-26 International Business Machines Corporation Apparatus and method for providing externalization in an object-oriented environment
US5890158A (en) 1997-03-31 1999-03-30 International Business Machines Corporation Method, apparatus, and program storage device for sharing objects with a network server and a database server using a common object model
US5878411A (en) 1997-06-27 1999-03-02 International Business Machines Corporation Dependent object class and subclass mapping to relational data store
US5887134A (en) 1997-06-30 1999-03-23 Sun Microsystems System and method for preserving message order while employing both programmed I/O and DMA operations
US5946694A (en) 1997-09-29 1999-08-31 International Business Machines Corporation Apparatus and method for transparent application of service to business objects

Patent Citations (99)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3449669A (en) * 1965-03-05 1969-06-10 Aga Ab Frequency control circuit transforming phase angle into frequency
US4567359A (en) * 1984-05-24 1986-01-28 Lockwood Lawrence B Automatic information, goods and services dispensing system
US4800488A (en) * 1985-11-12 1989-01-24 American Telephone And Telegraph Company, At&T Bell Laboratories Method of propagating resource information in a computer network
US4819233A (en) * 1987-04-08 1989-04-04 Westinghouse Electric Corp. Verification of computer software
US5724540A (en) * 1988-03-28 1998-03-03 Hitachi, Ltd. Memory system having a column address counter and a page address counter
US5341477A (en) * 1989-02-24 1994-08-23 Digital Equipment Corporation Broker for computer network server selection
US4992940A (en) * 1989-03-13 1991-02-12 H-Renee, Incorporated System and method for automated selection of equipment for purchase through input of user desired specifications
US6351735B1 (en) * 1989-05-01 2002-02-26 Catalina Marketing International, Inc. Check transaction processing, database building and marketing method and system utilizing automatic check reading
US20020073019A1 (en) * 1989-05-01 2002-06-13 David W. Deaton System, method, and database for processing transactions
US5555427A (en) * 1989-12-26 1996-09-10 Fujitsu Limited Distributed processing in a system of computers at terminals connected by a communication network
US5319542A (en) * 1990-09-27 1994-06-07 International Business Machines Corporation System for ordering items using an electronic catalogue
US5327559A (en) * 1990-10-23 1994-07-05 International Business Machines Corporation Remote and batch processing in an object oriented programming system
US5339477A (en) * 1991-01-07 1994-08-23 Ron Warner Associates Apparatus for removing coatings from fingernails
US5544040A (en) * 1991-08-09 1996-08-06 Gerbaulet; Jean-Pierre System for management of common purchase operations for goods and services
US5774729A (en) * 1991-12-19 1998-06-30 International Business Machines Corporation Event handling in a high level programming language environment
US5778179A (en) * 1991-12-26 1998-07-07 Kabushiki Kaisha Toshiba System for flexible distributed processing and transaction processing suitable for nested transaction
US5339430A (en) * 1992-07-01 1994-08-16 Telefonaktiebolaget L M Ericsson System for dynamic run-time binding of software modules in a computer system
US6263379B1 (en) * 1992-07-06 2001-07-17 Microsoft Corporation Method and system for referring to and binding to objects using identifier objects
US5307490A (en) * 1992-08-28 1994-04-26 Tandem Computers, Inc. Method and system for implementing remote procedure calls in a distributed computer system
US5764982A (en) * 1992-10-30 1998-06-09 International Business Machines Corporation Peer-to-peer communication interface
US5511196A (en) * 1992-11-17 1996-04-23 International Business Machines Corporation Method and system in a data processing system for the enhancement of relationships between reference objects in an object oriented environment and a data object outside an object oriented environment
US5548724A (en) * 1993-03-22 1996-08-20 Hitachi, Ltd. File server system and file access control method of the same
US5446901A (en) * 1993-06-30 1995-08-29 Digital Equipment Corporation Fault tolerant distributed garbage collection system and method for collecting network objects
US5548726A (en) * 1993-12-17 1996-08-20 Taligeni, Inc. System for activating new service in client server network by reconfiguring the multilayer network protocol stack dynamically within the server node
US5594921A (en) * 1993-12-17 1997-01-14 Object Technology Licensing Corp. Authentication of users with dynamically configurable protocol stack
US6031977A (en) * 1993-12-17 2000-02-29 Object Technology Licensing Corp. Object-oriented distributed communications directory service
US6360266B1 (en) * 1993-12-17 2002-03-19 Object Technology Licensing Corporation Object-oriented distributed communications directory system
US5745755A (en) * 1994-01-05 1998-04-28 Covey; Peter J. Method for creating and maintaining a database for a dynamic enterprise
US5664111A (en) * 1994-02-16 1997-09-02 Honicorp, Inc. Computerized, multimedia, network, real time, interactive marketing and transactional system
US5592375A (en) * 1994-03-11 1997-01-07 Eagleview, Inc. Computer-assisted system for interactively brokering goods or services between buyers and sellers
US5799173A (en) * 1994-07-25 1998-08-25 International Business Machines Corporation Dynamic workload balancing
US5715314A (en) * 1994-10-24 1998-02-03 Open Market, Inc. Network sales system
US5664110A (en) * 1994-12-08 1997-09-02 Highpoint Systems, Inc. Remote ordering system
US5889988A (en) * 1995-01-03 1999-03-30 Intel Corporation Debugger for debugging tasks in an operating system virtual device driver
US5491791A (en) * 1995-01-13 1996-02-13 International Business Machines Corporation System and method for remote workstation monitoring within a distributed computing environment
US5727048A (en) * 1995-03-01 1998-03-10 Fujitsu Limited Multimedia communication system with a multimedia server to terminals via a public network
US5940827A (en) * 1995-03-31 1999-08-17 Sun Microsystems, Inc. Methods and apparatus for managing a database in a distributed operating environment
US6363409B1 (en) * 1995-04-24 2002-03-26 Microsoft Corporation Automatic client/server translation and execution of non-native applications
US5721832A (en) * 1995-05-12 1998-02-24 Regal Greetings & Gifts Inc. Method and apparatus for an interactive computerized catalog system
US5790677A (en) * 1995-06-29 1998-08-04 Microsoft Corporation System and method for secure electronic commerce transactions
US5745703A (en) * 1995-07-18 1998-04-28 Nec Research Institute, Inc. Transmission of higher-order objects across a network of heterogeneous machines
US5734706A (en) * 1995-07-27 1998-03-31 Windsor; Victoria Brein Caller identification and data retrieval system
US5644720A (en) * 1995-07-31 1997-07-01 West Publishing Company Interprocess communications interface for managing transaction requests
US5737706A (en) * 1995-08-03 1998-04-07 Bell Atlantic Network Services, Inc. Power system supporting CDPD operation
US5710887A (en) * 1995-08-29 1998-01-20 Broadvision Computer system and method for electronic commerce
US5872973A (en) * 1995-10-26 1999-02-16 Viewsoft, Inc. Method for managing dynamic relations between objects in dynamic object-oriented languages
US6243814B1 (en) * 1995-11-02 2001-06-05 Sun Microsystem, Inc. Method and apparatus for reliable disk fencing in a multicomputer system
US5925108A (en) * 1995-11-03 1999-07-20 Novell, Inc. Event notification in a computer system
US5915112A (en) * 1996-01-02 1999-06-22 International Business Machines Corporation Remote procedure interface with support for multiple versions
US5887172A (en) * 1996-01-10 1999-03-23 Sun Microsystems, Inc. Remote procedure call system and method for RPC mechanism independent client and server interfaces interoperable with any of a plurality of remote procedure call backends
US5758328A (en) * 1996-02-22 1998-05-26 Giovannoli; Joseph Computerized quotation system and method
US5721825A (en) * 1996-03-15 1998-02-24 Netvision, Inc. System and method for global event notification and delivery in a distributed computing environment
US5732706A (en) * 1996-03-22 1998-03-31 Lockheed Martin Ir Imaging Systems, Inc. Ultrasonic array with attenuating electrical interconnects
US5706502A (en) * 1996-03-25 1998-01-06 Sun Microsystems, Inc. Internet-enabled portfolio manager system and method
US6101528A (en) * 1996-03-27 2000-08-08 Intel Corporation Method and apparatus for discovering server applications by a client application in a network of computer systems
US20030084204A1 (en) * 1996-04-23 2003-05-01 Ann M. Wollrath System and method for facilitating dynamic loading of "stub"information to enable a program operating in one address space to invoke processing of a remote method or procedure in another address space
US5778187A (en) * 1996-05-09 1998-07-07 Netcast Communications Corp. Multicasting method and apparatus
US5889951A (en) * 1996-05-13 1999-03-30 Viewpoint Corporation Systems, methods, and computer program products for accessing, leasing, relocating, constructing and modifying internet sites within a multi-dimensional virtual reality environment
US6018619A (en) * 1996-05-24 2000-01-25 Microsoft Corporation Method, system and apparatus for client-side usage tracking of information server systems
US5729594A (en) * 1996-06-07 1998-03-17 Klingman; Edwin E. On-line secured financial transaction system through electronic media
US6014686A (en) * 1996-06-21 2000-01-11 Telcordia Technologies, Inc. Apparatus and methods for highly available directory services in the distributed computing environment
US5748897A (en) * 1996-07-02 1998-05-05 Sun Microsystems, Inc. Apparatus and method for operating an aggregation of server computers using a dual-role proxy server computer
US20010011350A1 (en) * 1996-07-03 2001-08-02 Mahboud Zabetian Apparatus and method for electronic document certification and verification
US5742768A (en) * 1996-07-16 1998-04-21 Silicon Graphics, Inc. System and method for providing and displaying a web page having an embedded menu
US5758077A (en) * 1996-08-02 1998-05-26 Hewlett-Packard Company Service-centric monitoring system and method for monitoring of distributed services in a computing network
US5794207A (en) * 1996-09-04 1998-08-11 Walker Asset Management Limited Partnership Method and apparatus for a cryptographically assisted commercial network system designed to facilitate buyer-driven conditional purchase offers
US6212578B1 (en) * 1996-09-09 2001-04-03 Oracle Corporation Method and apparatus for managing dependencies in a distributed computing environment for ensuring the safety of remote procedure calls
US6757729B1 (en) * 1996-10-07 2004-06-29 International Business Machines Corporation Virtual environment manager for network computers
US6243716B1 (en) * 1996-10-11 2001-06-05 Sun Microsystems, Inc. Methods and systems for distributed failure detection and recovery using leasing
US6263350B1 (en) * 1996-10-11 2001-07-17 Sun Microsystems, Inc. Method and system for leasing storage
US6092194A (en) * 1996-11-08 2000-07-18 Finjan Software, Ltd. System and method for protecting a computer and a network from hostile downloadables
US5944793A (en) * 1996-11-21 1999-08-31 International Business Machines Corporation Computerized resource name resolution mechanism
US6028414A (en) * 1997-01-29 2000-02-22 H Power Enterprises Of Canada Inc. Fuel cell stand-by energy supply system
US6282581B1 (en) * 1997-03-27 2001-08-28 Hewlett-Packard Company Mechanism for resource allocation and for dispatching incoming calls in a distributed object environment
US6189046B1 (en) * 1997-03-27 2001-02-13 Hewlett-Packard Company Mechanism and method for merging cached location information in a distributed object environment
US6104716A (en) * 1997-03-28 2000-08-15 International Business Machines Corporation Method and apparatus for lightweight secure communication tunneling over the internet
US6408342B1 (en) * 1997-03-28 2002-06-18 Keith E. Moore Communications framework for supporting multiple simultaneous communications protocols in a distributed object environment
US6041351A (en) * 1997-04-17 2000-03-21 Newmoon.Com Network traffic by instruction packet size reduction
US6085030A (en) * 1997-05-02 2000-07-04 Novell, Inc. Network component server
US6378001B1 (en) * 1997-06-18 2002-04-23 International Business Machines Corp. Collaborative framework with shared objects
US5905868A (en) * 1997-07-22 1999-05-18 Ncr Corporation Client/server distribution of performance monitoring data
US6343308B1 (en) * 1997-08-14 2002-01-29 International Business Machines Corporation Systems, methods and computer programs for mixing different versions of Java classes
US6061699A (en) * 1997-11-03 2000-05-09 International Business Machines Corporation Method and computer program product for extracting translatable material from browser program function codes using variables for displaying MRI
US6016496A (en) * 1997-11-20 2000-01-18 International Business Machines Corporation Method and apparatus for an object-oriented object for retrieving information from local and remote databases
US6704803B2 (en) * 1998-01-26 2004-03-09 International Business Machines Corporation Method and system for distributing data events over an information bus
US6604127B2 (en) * 1998-03-20 2003-08-05 Brian T. Murphy Dynamic lookup service in distributed system
US6093216A (en) * 1998-05-29 2000-07-25 Intel Corporation Method of run-time tracking of object references in Java programs
US6269401B1 (en) * 1998-08-28 2001-07-31 3Com Corporation Integrated computer system and network performance monitoring
US6385643B1 (en) * 1998-11-05 2002-05-07 Bea Systems, Inc. Clustered enterprise Java™ having a message passing kernel in a distributed processing system
US6418468B1 (en) * 1998-12-03 2002-07-09 Cisco Technology, Inc. Automatically verifying the feasibility of network management policies
US6216158B1 (en) * 1999-01-25 2001-04-10 3Com Corporation System and method using a palm sized computer to control network devices
US6505248B1 (en) * 1999-03-24 2003-01-07 Gte Data Services Incorporated Method and system for monitoring and dynamically reporting a status of a remote server
US6603772B1 (en) * 1999-03-31 2003-08-05 Cisco Technology, Inc. Multicast routing with multicast virtual output queues and shortest queue first allocation
US6604140B1 (en) * 1999-03-31 2003-08-05 International Business Machines Corporation Service framework for computing devices
US6578074B1 (en) * 1999-06-25 2003-06-10 Mediaone Group, Inc. Provisioning server enhancement
US6564174B1 (en) * 1999-09-29 2003-05-13 Bmc Software, Inc. Enterprise management system and method which indicates chaotic behavior in system resource usage for more accurate modeling and prediction
US20020059212A1 (en) * 2000-10-23 2002-05-16 Nec Corporation Stub search loading system and method, server apparatus, client apparatus, and computer-readable recording medium
US20020111814A1 (en) * 2000-12-12 2002-08-15 Barnett Janet A. Network dynamic service availability
US20030005132A1 (en) * 2001-05-16 2003-01-02 Nortel Networks Limited Distributed service creation and distribution

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7143160B2 (en) * 2001-03-09 2006-11-28 Fujitsu Limited Event-driven information display system and event-driven information display method
US7546611B2 (en) * 2003-12-13 2009-06-09 Elecronics And Telecommunications Research Institute Driver agent device for supporting remote device driver development environment in embedded system and operation method thereof
US20050143907A1 (en) * 2003-12-13 2005-06-30 Kim Jeong S. Driver agent device for supporting remote device driver development environment in embedded system and operation method thereof
WO2005122720A3 (en) * 2004-06-10 2007-03-22 Cisco Tech Inc A generic framework for deploying ems provisioning services
US8327386B2 (en) 2005-01-14 2012-12-04 International Business Machines Corporation Mechanism that provides more efficient event handler processing
US8112765B2 (en) * 2005-01-14 2012-02-07 International Business Machines Corporation Mechanism that provides more efficient event handler processing
US20090254923A1 (en) * 2005-01-14 2009-10-08 International Business Machines Corporation Mechanism that Provides More Efficient Event Handler Processing
US7653681B2 (en) 2005-01-14 2010-01-26 International Business Machines Corporation Software architecture for managing a system of heterogenous network processors and for developing portable network processor applications
US20100106780A1 (en) * 2005-01-14 2010-04-29 International Business Machines Corporation Software Architecture for Managing a System of Heterogenous Network Processors and for Developing Portable Network Processor Applications
US7974999B2 (en) 2005-01-14 2011-07-05 International Business Machines Corporation Software architecture for managing a system of heterogenous network processors and for developing portable network processor applications
US20080182576A1 (en) * 2007-01-22 2008-07-31 Qualcomm Incorporated Message ordering for network based mobility management systems
US9392434B2 (en) * 2007-01-22 2016-07-12 Qualcomm Incorporated Message ordering for network based mobility management systems
US10681530B2 (en) 2007-01-22 2020-06-09 Qualcomm Incorporated Message ordering for network based mobility management systems
US11463861B2 (en) 2007-01-22 2022-10-04 Qualcomm Incorporated Message ordering for network based mobility management systems
US20080196006A1 (en) * 2007-02-06 2008-08-14 John Bates Event-based process configuration
US8656350B2 (en) * 2007-02-06 2014-02-18 Software Ag Event-based process configuration
US20110167431A1 (en) * 2010-01-05 2011-07-07 Seiko Epson Corporation Control of apparatus incorporating computer
US9436635B1 (en) * 2011-08-30 2016-09-06 Emc Corporation Leases in a heterogenous data environment

Also Published As

Publication number Publication date
US6272559B1 (en) 2001-08-07

Similar Documents

Publication Publication Date Title
US6272559B1 (en) Deferred reconstruction of objects and remote loading for event notification in a distributed system
US6487607B1 (en) Methods and apparatus for remote method invocation
US6393497B1 (en) Downloadable smart proxies for performing processing associated with a remote procedure call in a distributed system
US6253256B1 (en) Deferred reconstruction of objects and remote loading in a distributed system
US6983285B2 (en) Apparatus and method for dynamically verifying information in a distributed system
US6560656B1 (en) Apparatus and method for providing downloadable code for use in communicating with a device in a distributed system
US6134603A (en) Method and system for deterministic hashes to identify remote methods
EP0766172B1 (en) A method and apparatus for allowing generic stubs to marshal and unmarshal data in object reference specific data formats
US5566302A (en) Method for executing operation call from client application using shared memory region and establishing shared memory region when the shared memory region does not exist
US6629154B1 (en) Method and system for deterministic hashes to identify remote methods
US20020029297A1 (en) Method and apparatus for efficient representation of variable length identifiers in a distributed object system
US7089263B2 (en) Apparatus and method for dynamically verifying information in a distributed system
EP1405185A2 (en) Method and system for passing objects in a distributed system using serialization contexts
EP1057113B1 (en) Deferred reconstruction of objects and remote loading for event notification in a distributed system
WO1999044123A1 (en) Downloadable smart proxies for performing processing associated with a remote procedure call in a distributed system
EP1235149A2 (en) Deferred reconstruction of objects and remote loading for event notification in a distributed system
Diehl et al. Implementing Multi-User Worlds with CORBA

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION