Database application development system with improved methods for distributing and executing objects across multiple tiers

• US 6,006,230 A
• Filed: 01/29/1997
• Issued: 12/21/1999
• Est. Priority Date: 01/15/1997
• Status: Expired due to Term

• Current Assignee: Sybase Incorporated (SAP SE)
• Original Assignee: Sybase Incorporated (SAP SE)
• Inventors: Ludwig, Patrick B., Marlow, Scott P.
• Primary Examiner(s): Fetting, Anton
• Assistant Examiner(s): ROBINSON, GRETA LEE
• Application Number:
  US08/791,800
• Time in Patent Office: 1,056 Days
• Field of Search: 707/102, 707/103, 707/104, 707/10, 395/701, 395/710
• US Class Current: 1/1
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A database client/server development system providing support for remote sessions with user-created application objects is described. When a user desires to create a "remoteable" object from a user object, the user assigns a proxy name or alias, thereby providing a mechanism to differentiate the real (local) version of the object from a remote version of that object. When the user creates the proxy, the system generates all of the interface definitions for the object (i.e., to access its internal functionality) which are capable of being proxied (i.e., "proxiable"). A given object can reside locally, remotely, or both; the proxy mechanism allows the application to resolve at runtime which version of the object to invoke. When the user'"'"'s final application is deployed, the proxy object is deployed at the client machine for use at the client for accessing the real version at the server. If desired, an application can be deployed with a real copy of the object, in addition to the proxy. In such a case, the client can serve as a server (of that object), in addition to being a client of objects from other servers.

Claims

1. In a distributed computing system comprising at least one client in communication with at least one server, a method for executing a distributed application comprising distributed application objects, the method comprising:

for a particular application object of said distributed application, creating at a particular client a proxy object corresponding to said particular application object, said proxy object comprising an interface definition for said particular application object thereby allowing said particular client to invoke methods of a remote object that implements said particular application object;

creating at a particular server said remote object, said remote object providing a run-time instantiation of said particular application object and including properties and methods of said particular application object;

establishing a connection between said particular client and said particular server;

executing at the particular client an application which requires services of said particular application object; and

in response to requests from the particular client for invoking services of said particular application object, invoking the proxy object at the particular client, whereupon the proxy object invokes corresponding services at the remote object and, thereafter, returns results back to said application.

2. The method of claim 1, wherein said remote object comprises a non-visual object instantiated from an object-oriented class.

3. The method of claim 2, wherein said remote object comprises properties stored as object data, together with access to methods defined by the class.

4. The method of claim 3, wherein the proxy object comprises an interface providing access to the object data and class methods available at the remote object.

5. The method of claim 1, wherein said creating a proxy object step includes assigning an alias to the proxy object for differentiating it from the corresponding remote object.

6. The method of claim 1, further comprising:

storing a copy of the remote object locally at the client, so that the executing application can invoke a local copy of the remote object, as desired.

7. The method of claim 6, wherein said application determines during runtime execution which version of the remote object to invoke.

8. The method of claim 1, wherein said remote object comprises a non-visual object contained within a visual object.

9. The method of claim 1, further comprising:

deploying the application at the particular client with a copy of the remote object, so that said particular client can function as a server for yet another client.

10. The method of claim 1, wherein said executing step includes:

receiving a request from the application at the proxy object for invoking a particular method of the remote object, said request specifying a list of parameters by which the particular method is to be invoked.

11. The method of claim 10, wherein said parameters include data members passed by value.

12. The method of claim 10, wherein said parameters include data members passed by reference.

13. The method of claim 10, wherein said parameters include nested data members.

14. The method of claim 10, further comprising:

packing said parameter list into a byte stream for transport across a network to the remote object.

15. The method of claim 1, wherein said proxy object includes stubs for methods which exist at the remote object.

16. The method of claim 1, wherein a plurality of proxy objects are created at various clients in communication with the server, all such proxy objects referencing corresponding remote objects residing at the particular server.

17. The method of claim 1, wherein a plurality of proxy objects are created at various clients, for referencing corresponding remote objects, each residing on a different server.

18. The method of claim 1, wherein at least one of the clients in the system functions as a server to another client by storing a remote object for that other client.

19. The method of claim 1, wherein application logic for the application is distributed across n number of tiers, wherein n represents how many remote objects have been created on computers other than that which the application is currently executing.

20. The method of claim 1, wherein said connecting step includes establishing a connection between the particular client and the particular server using a TCP/IP communication driver.

21. In a distributed computing environment comprising one or more clients connected to one or more servers, a method for partitioning application objects among multiple computers so that objects can be invoked across an arbitrary number of tiers of computers, the method comprising:

(a) establishing a connection between a particular client and a particular server;

(b) receiving at the particular client a request to partition application objects by creating an object instance of a particular object which resides at the server;

(c) in response to the request, partitioning application objects by creating an object instance of the particular object at the particular server and creating a corresponding proxy object for said particular object at the particular client, the proxy object defining properties for the object instance for said particular object and defining an interface for executing methods available to said object instance; and

(d) executing the application at the particular client by invoking through the proxy object methods available to the object instance.

22. The method of claim 21, wherein steps (a)-(d) are repeated for a plurality of different servers, so that said application objects can be partitioned among an arbitrary number of computers.

23. The method of claim 21, wherein said establishing a connection step includes establishing a connection session between the particular client and the particular server through a communication driver.

24. The method of claim 23, wherein said communication driver is a selected one of TCP/IP and named pipes communication drivers.

25. The method of claim 21, further comprising:

creating a copy of the object instance at the particular client so that methods available to the object instance can be invoked locally.

26. The method of claim 21, wherein creation of the proxy object at the client occurs at runtime during execution of the application.

27. The method of claim 21, wherein said interface of the proxy object includes names of methods which can be invoked by the object instance.

28. The method of claim 21, wherein step (d) includes:

transmitting parameter information across a network from the proxy object to the object instance.

29. The method of claim 28, wherein said parameter information includes at least one data value having a data type.

30. The method of claim 28, wherein said transmitting parameter information step includes:

converting nested data structure information into a flat byte stream suitable for transmission across the network.

31. A system for partitioning and executing an application comprising:

a client computer for executing a client application, said client computer storing a proxy object defining an interface for a particular object, thereby allowing said client application to communicate with a remote object that is a run-time instance of said particular object;

a server computer for creating an instance of the remote object, in response to a request from the client application at the proxy object for invoking a method of the remote object; and

an object manager for establishing a connection between the proxy object and the instance of the remote object and for forwarding requests received at the proxy object for invoking the method available to the instance of the remote object, so that execution of the application is partitioned among any number of computers.

32. The system of claim 31, wherein implementation of the method of the instance of the remote object resides at the server computer.

33. The method of claim 32, wherein said proxy object stores an interface defining methods which can be invoked at the remote object.

34. The system of claim 33, wherein said interface includes information identifying a method by name and characterizing parameters which the method is expected to receive upon invocation.

35. The system of claim 31, wherein methods of the remote object can be invoked with method arguments passed by value or by reference.