Abstract: A self-healing grid mechanism using peer-to-peer platform protocols. In one embodiment, two or more nodes on a grid may be configured as master nodes. One of the configured master nodes may serve as the actual master node, and one may be backup or “shadow” master node, not actively serving as a master node. If the active master node goes down, the peer-to-peer protocols may be used to detect that the master node is not active and the backup master node may take over the master node operations for the grid. The backup master node may “shadow” the master node, keeping updated information about the grid configuration and operations via the peer-to-peer platform protocols, so that it can assume grid management operations seamlessly.

Abstract: An autonomic grid computing mechanism. In embodiments, peer-to-peer platform protocols may be integrated with a grid computing system. Embodiments may use peer-to-peer platform protocols as the transport for the grid computing system. Embodiments may provide one or more of, but not limited to, the following capabilities to grid computing systems: self-deployment and self-configuration, self-updating, self-healing, node removal, master node backup, monitoring, administration, load balancing, grid brokering, decentralized grid, and multi-grid support. Peer-to-peer platform protocols may be used to automatically configure compute nodes. When a node comes up, the node searches for a master node using the peer-to-peer platform. When the node finds a master node, it provides node information to the master node using the peer-to-peer platform. The master node may send the node grid configuration information using the peer-to-peer platform and the node may self-configure as a compute node.

Abstract: A mobile agent may be provided for collaborative content control in peer-to-peer networks. A peer may launch a mobile agent including an itinerary of peers to be visited and indications of one or more documents that the peers are collaboratively editing. The mobile agent may visit peers indicated by the itinerary to collect version information for the document(s). The mobile agent may return the version information to the initiating peer, which may coordinate each of the document(s) on the peer to a most recent version in accordance with the version information provided by the mobile agent. Visited peers may use the payload to determine if their version of the document(s) are up to date and, if not, may add a version update request to the payload. The initiating peer may send the most recent version information to peers that added version update requests to the payload.

Abstract: Embodiments of a system and method for using mobile agents for collaborative content control in peer-to-peer networks. A peer may launch a mobile agent including an itinerary of peers to be visited and indications of one or more documents that the peers are collaboratively editing. The mobile agent may visit peers indicated by the itinerary to collect version information for the document(s). The mobile agent may return the version information to the initiating peer, which may coordinate each of the document(s) on the peer to a most recent version in accordance with the version information provided by the mobile agent. Visited peers may use the payload to determine if their version of the document(s) are up to date and, if not, may add a version update request to the payload. The initiating peer may send the most recent version information to peers that added version update requests to the payload.