Object Request Broker: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''Object Request Brokers''' (ORB) allow unique objects that have state and identity to be distributed |
'''Object Request Brokers''' (ORB) allow unique objects that have state and identity to be distributed |
||
across a network. The greatest advantage compared to RPC is the possibility to invoke methods on |
across a network. The greatest advantage compared to remote procedure calls (RPC) is the possibility to invoke methods on |
||
remote object instances (not only application procedures). |
remote object instances (not only application procedures). |
||
In contrast to TP Monitors, ORBs are simply communications backbones that are used to access unique |
In contrast to [[Transaction processing monitor|TP Monitors]], ORBs are simply communications backbones that are used to access unique |
||
remote objects. |
remote objects. |
||
Latest revision as of 07:34, 17 November 2004
Object Request Brokers (ORB) allow unique objects that have state and identity to be distributed across a network. The greatest advantage compared to remote procedure calls (RPC) is the possibility to invoke methods on remote object instances (not only application procedures). In contrast to TP Monitors, ORBs are simply communications backbones that are used to access unique remote objects.