Oracle International Corporation

Sun Microsystems, Inc.

Oracle America, Inc.

Oracle International Corpration

Harold Carr

Mark S Moir

Maurice P Herlihy

Mark Sean Moir

Isaac Sheff

Ken M Cavanaugh

Thulasiraman Jeyaraman

Ryan Eberhard

Uday Madhusudan Joshi

Mitchell Upton

Alex Kogan

Prashant Agarwal

Victor Cacciari Miraldo

Shing Wai Chan

A sharded, permissioned, distributed ledger may reduce the amount of work and communication required by each participant, thus possibly avoiding scalability bottlenecks that may be inherent in previous distributed ledger implementations and possibly enabling the use of additional resources to translate to increased throughput. A sharded, permissioned, distributed ledger may be made up of multiple shards, each of which may also be a distributed ledger and which may operate in parallel. Participation within a sharded, permissioned, distributed ledger may be allowed only with permission of an authority. A sharded, permissioned, distributed ledger may include a plurality of nodes, each including a dispatcher configured to receive transaction requests from clients and to forward received requests to verifiers configured to append transactions to individual ones of the shards.

Sharded permissioned distributed ledgers

An authenticated modular map library may support partial state for a key-value store. A key-value store may be created that is organized as a tree data structure that divides items into pages. Features to access the key-value store may also be specified when the key-value store is created. A portion of the key-value store may be sent to a participant of a blockchain network, which may attempt to access an item to be found in a page in the key-value store according to the specified features. If the page is not included in the portion, the page may be requested from another participant, received, and verified before being used to complete the attempted access of the item.

Authenticated key-value stores supporting partial state

A system and method can support asynchronous request/response in a network environment. A network protocol can utilize a load balancer to balance requests, such as HTTP requests, over a fast network interface, such as InfiniBand, to one or more nodes of an application server cluster. The system and method can attach headers to the requests such that the requests can be sent in an interleaved manner. The system and method can further allow for sending of large requests by breaking up the large requests into smaller portions, and sending each portion, interleaved, with other requests.

System and method for supporting asynchronous request/response in a network environment

The present disclosure relates generally to techniques for improving reliability of message communications. In certain embodiments, techniques are described for facilitating reliable communication of messages between a source (e.g., a client system) and a destination (e.g., a target system) via an intermediary communication handler system. In certain embodiments, a message can include a request to be communicated to a destination for a target service. An intermediary communication handler system can store information indicative of the delivery status for a message to ensure reliable communication. The information indicative of the delivery status for a message can be managed in association with a unique identifier corresponding to the message. The information indicative of the delivery status for a message may also be used to determine whether to retry communication of a message in satisfaction of reliability parameters (e.g., QoS criteria) specified for a communication protocol used for communication of the message.

Techniques for reliable messaging for an intermediary in a network communication environment

A system and method for providing a dynamic invocation and service interface for use in a middleware or other environment. At the service-side, messages can be inserted into an inbound processing chain. After service-side inbound processing, messages are given to the user via a provider request function. The user gives a response by using a provider response function that inserts messages into a service-side outbound processing chain. After service-side outbound processing, messages are given to the user's service response transport. On the client side, the user can insert messages into the outbound processing chain using a dispatcher request. After client-side outbound processing, messages are given to the user's client request transport. This decouples message processing from the transport and makes the message processing asynchronous in nature. When the response is received, a user uses a client response transport function to insert the response into the client-side inbound processing chain.

System and method for providing a dynamic invocation and service interface for use in a middleware or other environment

A method for servicing requests in a dynamic cluster that includes receiving, by a first replica of the dynamic cluster, a first request that includes a first membership label from a client, wherein the client stores the first membership label and a first cluster list, determining whether the first membership label is obsolete, and sending a second membership label and a second cluster list to the client when the first membership label is obsolete, wherein the client updates the first cluster list with the second cluster list.

Method and system for servicing requests in a dynamic cluster

Method and apparatus for determining data encoding format in RMI-IIOP messages. Embodiments may provide a mechanism to use Java serialization rather than, or as an alternative to, CORBA Common Data Representation (CDR), for the marshaling and unmarshaling of data in RMI-IIOP message exchanges. In one embodiment, a server-side Object Request Broker (ORB) may be configured to support the encoding of data in RMI-IIOP messages in accordance with CDR encoding and Java serialization encoding. In one embodiment, an Interoperable Object References (IOR) published by the server may include information that indicates which encoding type(s) are supported by the server-side ORB on the server that hosts the associated object. A client-side ORB may optionally use Java serialization or CDR as the data encoding format for RMI-IIOP messages to invoke the associated object on the server. Each RMI-IIOP message may include an indication of which encoding type is used in the message.

Method and apparatus for determining data encoding format in RMI-IIOP messages

Method and apparatus for RMI-IIOP implementation using Java serialization as a data encoding mechanism. Embodiments may provide a mechanism to use Java serialization rather than, or as an alternative to, CORBA Common Data Representation (CDR), for the marshaling and unmarshaling of data in RMI-IIOP message exchanges. In one embodiment, a server-side Object Request Broker (ORB) may be configured to support the encoding of data in RMI-IIOP messages in accordance with CDR encoding and Java serialization encoding. A client-side ORB may optionally use Java serialization or CDR as the data encoding format for RMI-IIOP messages to invoke the associated object on the server. Response messages from the server to the client may include data encoded according to Java serialization or CDR.

Method and apparatus for RMI-IIOP implementation with java serialization

Method and apparatus for dynamically and adaptively alternating encodings, protocols, and/or transports in remoting system clients. Embodiments may provide a mechanism or mechanisms to isolate encoding, protocol, and/or transport changes in remoting system clients. In a remoting system, a server may make its service(s) available via multiple encoding, protocol and transport (EPT) combinations. One embodiment may provide a mechanism that enables a remoting system client to select an EPT combination for sending messages to a server, to have that choice drive the creation of objects and/or interface instances on the remoting system client used in the message exchange, and to switch to a different EPT combination on the remoting system client if necessary or desired. Embodiments may be used in all types of remoting systems and/or in other computing environments including, but not limited to, peer-to-peer environments.

Method and apparatus to isolate changes in remoting system clients

Method and apparatus for dynamically and adaptively alternating encodings, protocols, and/or transports in remoting system servers. Embodiments may provide a mechanism or mechanisms to isolate encoding, protocol, and/or transport changes in remoting system servers. In a remoting system, a server may make its service(s) available via multiple, published encoding, protocol and transport (EPT) combinations. One embodiment may provide a mechanism that enables a remoting system server to determine an EPT combination for receiving messages from a client, to have that choice drive the creation of objects and/or interface instances on the remoting system server used in the message exchange (including, but not limited to, connections, protocol handlers, and decoders), and to switch to a different EPT combination on the remoting system server to receive other messages, if necessary. Embodiments may be used in all types of remoting systems and/or in other computing environments including, but not limited to, peer-to-peer environments.

Growing community of inventors

Salt Lake City, UT, United States of America

Harold Carr