Abstract: The present disclosure generally relates to harvesting geothermal energy from mature and near end-of-life oil and gas reservoirs that have been subjected to secondary oil recovery steam processes like steam-assisted gravity drainage (SAGD), steamflood, etc. The geothermal potential of these mature SAGD reservoirs can be used to generate green electricity thus reducing the greenhouse gas (GHG) footprint of the oil production. Lateral spacing of injectors and producers, with closing of unused members of a well-pair for energy recovery is described.

Abstract: In order to enable a dynamic handshake procedure, a device may be configured with a list of handshake contributors. Contributors with connection handshake properties may be added to the contributor list. To perform handshake, the contributor list is processed to extract the connection handshake properties of each contributor to the handshake. Handlers for handling the connection handshake properties may also be dynamically added and invoked when a handshake is received.

Abstract: In order to enable a dynamic handshake procedure, a device may be configured with a list of handshake contributors. Contributors with connection handshake properties may be added to the contributor list. To perform handshake, the contributor list is processed to extract the connection handshake properties of each contributor to the handshake. Handlers for handling the connection handshake properties may also be dynamically added and invoked when a handshake is received.

Abstract: In developing applications for a plurality of node types, a meta-data definition of the application can be captured into an application definition module. The meta-data definition can describe the application for the plurality of node types. A code generation module can then automatically generate the application code for the plurality of node types. The code can be compiled per node type and the packaging necessary to deploy the application to the plurality of node types can also be automatically generated.

Abstract: In order to enable a dynamic handshake procedure, a device may be configured with a list of handshake contributors. Contributors with connection handshake properties may be added to the contributor list. To perform handshake, the contributor list is processed to extract the connection handshake properties of each contributor to the handshake. Handlers for handling the connection handshake properties may also be dynamically added and invoked when a handshake is received.

Abstract: In order to enable a dynamic handshake procedure, a client device is configured with a list of handshake contributors. The client device initiates a handshake by determining the handshake contributors and writing properties of the handshake contributors in a client handshake, which is then sent to a server device. The client handshake is processed at the server device by invoking an appropriate handler, which handles the handshake result. The server can also send its contributors and their properties to the client. Once the client receives the properties, the client can call an appropriate handler to handle the properties. Connections may be created based on the exchanged properties. New contributors and contributor handlers may be added to both the client and server devices.

Abstract: In order to manage stale data on a network of computer systems, a file harvester agent may be configured with a list of stale data files to be deleted. The file harvester agent may be deployed to the computer systems of a network. When executed in a computer system, the file harvester agent searches the file system of the computer system to locate any files or data indicated in the file list. Any located data files are deleted. Once the agent has finished processing the file list on a computer system, the agent can copy or replicate itself to other computer systems of the network in accordance with a pre-configured itinerary.

Abstract: In distributed object computing, messages from a source node to a destination node are often required to be routed via one or more intermediate nodes. In order to enhance efficiency of the relay process, a message envelope of a message may include a node list field that specifies the routing path of the message. The communication protocol for communicating the message may specify that when a message is received into a particular node, the node analyzes the node list field. If the identity of the node is last in the node list field, then the node is the destination node and thus the node unmarshals the message. Otherwise, the node forwards the message to the next node in the field list without unmarshalling the message.

Abstract: In developing applications for a plurality of node types, a meta-data definition of the application can be captured into an application definition module. The meta-data definition can describe the application for the plurality of node types. A code generation module can then automatically generate the application code for the plurality of node types, including transaction aware code. The code can be compiled per node type and the packaging necessary to deploy the application to the plurality of node types can also be automatically generated.

Abstract: In developing applications for a plurality of node types, a meta-data definition of the application can be captured into an application definition module. The meta-data definition can describe the application for the plurality of node types. A code generation module can then automatically generate the application code for the plurality of node types. The code can be compiled per node type and the packaging necessary to deploy the application to the plurality of node types can also be automatically generated.

Abstract: In order to enable a dynamic handshake procedure, a device may be configured with a list of handshake contributors. Contributors with connection handshake properties may be added to the contributor list. To perform handshake, the contributor list is processed to extract the connection handshake properties of each contributor to the handshake. Handlers for handling the connection handshake properties may also be dynamically added and invoked when a handshake is received.

Abstract: In order to enable a dynamic handshake procedure, a client device is configured with a list of handshake contributors. The client device initiates a handshake by determining the handshake contributors and writing properties of the handshake contributors in a client handshake, which is then sent to a server device. The client handshake is processed at the server device by invoking an appropriate handler, which handles the handshake result. The server can also send its contributors and their properties to the client. Once the client receives the properties, the client can call an appropriate handler to handle the properties. Connections may be created based on the exchanged properties. New contributors and contributor handlers may be added to both the client and server devices.

Abstract: In developing applications for a plurality of node types, a meta-data definition of the application can be captured into an application definition module. The meta-data definition can describe the application for the plurality of node types. A code generation module can then automatically generate the application code for the plurality of node types. The code can be compiled per node type and the packaging necessary to deploy the application to the plurality of node types can also be automatically generated.

Abstract: During communication of a large data message from a client application to a server application, requirements to communicate smaller control messages can arise. To facilitate timely communication of control messages, a client application may include a chunking module that divides a data message into chunks that can be sent as a sequence of individual data message packets. When a control message needs to be sent, the sequence of data message packets can be interrupted to send a control message packet. At the server application, the sequence of message packets is processed so that data message packets are appended to a data message and control messages are extracted for immediate processing.

Abstract: In distributed object computing, messages from a source node to a destination node are often required to be routed via one or more intermediate nodes. In order to enhance efficiency of the relay process, a message envelope of a message may include a node list field that specifies the routing path of the message. The communication protocol for communicating the message may specify that when a message is received into a particular node, the node analyzes the node list field. If the identity of the node is last in the node list field, then the node is the destination node and thus the node unmarshals the message. Otherwise, the node forwards the message to the next node in the field list without unmarshalling the message.

Abstract: In order to manage stale data on a network of computer systems, a file harvester agent may be configured with a list of stale data files to be deleted. The file harvester agent may be deployed to the computer systems of a network. When executed in a computer system, the file harvester agent searches the file system of the computer system to locate any files or data indicated in the file list. Any located data files are deleted. Once the agent has finished processing the file list on a computer system, the agent can copy or replicate itself to other computer systems of the network in accordance with a pre-configured itinerary.

Abstract: During communication of a large data message from a client application to a server application, requirements to communicate smaller control messages can arise. To facilitate timely communication of control messages, a client application may include a chunking module that divides a data message into chunks that can be sent as a sequence of individual data message packets. When a control message needs to be sent, the sequence of data message packets can be interrupted to send a control message packet. At the server application, the sequence of message packets is processed so that data message packets are appended to a data message and control messages are extracted for immediate processing.

Abstract: In order to manage stale data on a network of computer systems, a file harvester agent may be configured with a list of stale data files to be deleted. The file harvester agent may be deployed to the computer systems of a network. When executed in a computer system, the file harvester agent searches the file system of the computer system to locate any files or data indicated in the file list. Any located data files are deleted. Once the agent has finished processing the file list on a computer system, the agent can copy or replicate itself to other computer systems of the network in accordance with a pre-configured itinerary.

Abstract: In developing applications for a plurality of node types, a meta-data definition of the application can be captured into an application definition module. The meta-data definition can describe the application for the plurality of node types. A code generation module can then automatically generate the application code for the plurality of node types, including transaction aware code. The code can be compiled per node type and the packaging necessary to deploy the application to the plurality of node types can also be automatically generated.

Abstract: A method for determining the lifespan of an agent utilizing a rule engine and a set of canonical survival rules, in an execution environment comprising collecting a survival rule, asserting a survival data into a working memory and executing the rule engine with the set of survival rules and the working memory.