System for object cloing and state synchronization across a network node tree

• US 20040168174A1
• Filed: 03/17/2004
• Published: 08/26/2004
• Est. Priority Date: 03/08/2000
• Status: Abandoned Application

• Current Assignee: Daisoft Incorporated
• Original Assignee: Daisoft Incorporated
• Inventors: Baker, Tyler Foley
• Application Number:
  US10/708,646
• Publication Number:
  US 20040168174A1
• Time in Patent Office: Days
• US Class Current: 719/310
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

The invention is a network node tree where a root node computer at the top of the network node tree has one or more branch node computers or leaf node computers maintaining a network connection to it at any given time. Each branch node computer may have one or more branch node computers or leaf node computers maintaining a network connection to it at any given time, thereby forming a network node tree starting at the top with the root node computer. In the network node tree a set of distributable objects, whose origination resides on the root node computer, are cloned and dispatched to descendant branch node computers and descendant leaf node computers. If a change is made to the “state” of a distributable object on the root node computer, that change is reflected throughout the entire network node tree to the corresponding cloned distributable object residing on each descendant branch node computer and descendant leaf node computer.

Claims

1. A distributed object messaging system comprising of:

a process of distributed object synchronization across a network node tree in which the root node and the branch nodes act in combination as a centralized server with

a) a network node tree where a root node computer at the top of the network node tree has a plurality of branch node computers maintaining a network connection to it at any given time,

b) in which each branch node computer may have one or more branch node computers maintaining a network connection to it at any given time,

c) a set of distributable objects, whose origination resides on the root node computer, are cloned and transmitted across the network connection to descendant branch node computers,

d) where if a change is made to the distributable object on the root node computer, that change is redispatched across the network connection to the distributable object residing on each descendant branch node computer,

e) with a security controller in said root node computer environment,

f) with said security controller creating a security controller clone,

g) with said security controller clone creating an authentication interface in the connecting computer,

h) with said authentication interface creating authentication data,

i) with said authentication data is transmitted to the root node,

j) with said root node using the authentication data to authenticate the connecting compute,

k) where if validated the root node returns registration data to the branch node, and

l) where a connection tree manager controls the placement of the connecting computer on the network node tree.

2. The system, as set forth in claim 1, wherein:

said branch nodes and said root nodes may have leaf nodes where said leaf nodes treated like branch nodes by the system.

3. The system, as set forth in claim 1, wherein:

a new peer connecting to an already existing peer on the network can download the synchronized state of these data objects without having to get said data from the original host.

4. The system, as set forth in claim 1, where a connection tree manager instructs all nodes where to connect to the network.

5. The system, as set forth in claim 2, wherein:

a change made to the state of a distributable object on a root node computer, said change is made to each of the distributable objects on all the descendant branch nodes and all of the descendant leaf nodes.

6. The system, as set forth in claim 1, wherein:

a root server is created and said root server forms an I/O channel through a TCP/IP socket.

7. A distributed object messaging system comprising of:

a process of distributed object synchronization across a network node tree in which the root node and the branch nodes act in combination as a centralized server with

a) a network node tree where a root node computer at the top of the network node tree has a plurality of branch node computers maintaining a network connection to it at any given time,

b) in which each branch node computer may have one or more branch node computers maintaining a network connection to it at any given time,

c) a set of distributable objects, whose origination resides on the root node computer, are cloned and transmitted across the network connection to descendant branch node computers,

d) where if a change is made to the distributable object on the root node computer, that change is redispatched across the network connection to the distributable object residing on each descendant branch node computer,

e) with a security controller in said root node computer environment,

f) with said security controller creating a security controller clone,

g) with said security controller clone creating an authentication interface in the connecting computer,

h) with said authentication interface creating authentication data,

i) with said authentication data is transmitted to the root node,

j) with said root node using the authentication data to authenticate the connecting compute,

k) where if validated the root node returns registration data to the branch node, and

l) where a connection tree manager controls the placement of the connecting computer on the network node tree.

8. The system, as set forth in claim 7, wherein:

said branch nodes and said root nodes may have leaf nodes where said leaf nodes treated like branch nodes by the system.

9. The system, as set forth in claim 7, wherein:

a new peer connecting to an already existing peer on the network can download the synchronized state of these data objects without having to get said data from the original host and where a connection tree manager instructs all nodes where to connect to the network.

10. The system, as set forth in claim 7, wherein:

a root server is created and said root server forms an I/O channel through a TCP/IP socket.