Abstract: Method and System for load balance of Common Object Request Broker Architecture (CORBA) object servers, comprising: invoking a name service cluster, indicating to a user whether bind interceptors are in use, and providing the user with a class having relevant methods if bind interceptors are in use.

Abstract: Methods and systems for load balancing of Common Object Request Broker Architecture (CORBA) object servers. A name service cluster is invoked. It is indicated to a user whether bind interceptors are in use. The user is provided with a class having relevant methods if bind interceptors are in use. The class that contains the most relevant methods is specified. Name service clusters are established for object servers where each name service cluster contains a unique object binding table containing object server reference bindings. Object server reference bindings having identical names are clustered into common clusters. A load balance is performed by having a name service select an object server located in an invoked cluster. A cluster component is appended to the invoked cluster to provide failover upon failover of the object server; and a selected object server reference binding is forwarded to a client upon completion of the load balance.

Abstract: A naming service clustering method which permits naming service load balancing over a set of object references contained within the same cluster such that loads are equitably distributed among servers. Each cluster contains its own unique object binding table which contains object references which each typically represent a single server. Load balancing is performed using a load balance algorithm (e.g., Round Robin). The specific algorithm which is used to perform load balancing is specified upon creation of each naming service cluster. The method provides transparent load balancing among multiple object references in the same cluster. In addition. transparent “failover” among object references in the same cluster is achieved. The method also provides a dynamic addition of new object references into a cluster via binding, along with the dynamic removal of old object references from a cluster via unbinding.

Abstract: A naming service clustering method which permits naming service load balancing over a set of object references contained within the same cluster such that loads are equitably distributed among servers. Each cluster contains its own unique object binding table which contains object references which each typically represent a single server. Load balancing is performed using a load balance algorithm (e.g., Round Robin). The specific algorithm which is used to perform load balancing is specified upon creation of each naming service cluster. The method provides transparent load balancing among multiple object references in the same cluster. In addition, transparent “failover” among object references in the same cluster is achieved. The method also provides a dynamic addition of new object references into a cluster via binding, along with the dynamic removal of old object references from a cluster via unbinding.

Abstract: A system and methodology for cross language type system compatibility is described. In one embodiment, for example, a system for translation of data types between a first application in a first language and a second application in a second language is described that comprises: a formal mapping between data types of the first language and data types of the second language; translators for translating data types between the first language and the second language based on the formal mapping; a translation mapping to the translators based on actual data types of the first application and formal data types of the second application; and a module for selecting an appropriate translator for translating between a particular data type in the first language and a data type in the second language based on the translation mapping in response to invocation of a method of the first application with the particular data type.

Abstract: The bidding method for selecting a protocol involves generating a bid for each protocol and ranking the bids in a prescribed order such that the order of the bids reflects the order of preference among the protocols. Thereafter, the most preferred protocol is executed or processes to establish the intended communication. If for some reason the more preferred protocol is unsuccessful, the next best protocol according to the order of the bids is processed. The bids are generated according to system/user set configuration and target object constraints. Bids fall into ranges of bid values where each range indicates a certain priority and associated rules.

Abstract: A naming service clustering method which permits naming service load balancing over a set of object references contained within the same cluster such that loads are equitably distributed among servers. Each cluster contains its own unique object binding table which contains object references which each typically represent a single server. Load balancing is performed using a load balance algorithm (e.g., Round Robin). The specific algorithm which is used to perform load balancing is specified upon creation of each naming service cluster. The method provides transparent load balancing among multiple object references in the same cluster. In addition, transparent “failover” among object references in the same cluster is achieved. The method also provides a dynamic addition of new object references into a cluster via binding, along with the dynamic removal of old object references from a cluster via unbinding.

Abstract: The bidding method for selecting a protocol involves generating a bid for each protocol and ranking the bids in a prescribed order such that the order of the bids reflects the order of preference among the protocols. Thereafter, the most preferred protocol is executed or processes to establish the intended communication. If for some reason the more preferred protocol is unsuccessful, the next best protocol according to the order of the bids is processed. The bids are generated according to system/user set configuration and target object constraints. Bids fall into ranges of bid values where each range indicates a certain priority and associated rules.