Browser-to-browser, dom-based, peer-to-peer communication with delta synchronization

• US 20030101235A1
• Filed: 09/03/2002
• Published: 05/29/2003
• Est. Priority Date: 09/04/2001
• Status: Active Grant

• Current Assignee: Chenglin Zhang
• Original Assignee: Chenglin Zhang
• Inventors: Zhang, Chenglin
• Granted Patent: US 6,865,599 B2
• Time in Patent Office: Days
• US Class Current: 709/218
• CPC Class Codes: H04L 12/1827 Network arrangements for conference optimisation or adaptation
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/18 Commands or executable codes
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A peer-to-peer communication system for use over an underlying computer network system, the peer-to-peer communication system comprising: at least two peers, each peer comprising: a Web browser; and a broker interposed between the browser and the underlying computer network system, with the broker being adapted to (1) monitor a first event taking place within the browser, encode the first event and associated changes in a first event message, and push the first event message to the at least one other peer over the underlying computer network system, whereby the at least one other peer can reproduce on the at least one other peer the changes associated with the first event; and (2) receive a second event message from the at least one other peer, where the second event message has been encoded to correspond to a second event and associated changes taking place on the at least one other peer, decode the second event message and push the results to the browser, whereby to recreate the changes associated with the second event within the browser.

Claims

1. A peer-to-peer communication system for use over an underlying computer network system, said peer-to-peer communication system comprising:

at least two peers, each said peer comprising;

a Web browser; and

a broker interposed between said browser and the underlying computer network system, with said broker being adapted to (1) monitor a first event taking place within said browser, encode said first event and associated changes in a first event message, and push said first event message to said at least one other peer over the underlying computer network system, whereby said at least one other peer can reproduce on said at least one other peer the changes associated with the first event; and

(2) receive a second event message from said at least one other peer, where said second event message has been encoded to correspond to a second event and associated changes taking place on said at least one other peer, decode said second event message and push the results to said browser, whereby to recreate the changes associated with the second event within said browser.

2. A peer-to-peer communication system according to claim 1 wherein the changes are recreated by creating the second event and reposting the second event on the browser.

3. A peer-to-peer communication system according to claim 1 wherein the underlying computer network system comprises an Instant Messenger (TM) system, and said broker is adapted to communicate with said at least one other peer over the Instant Messenger system.

4. A peer-to-peer communication system according to claim 3 wherein the Instant Messenger (IM) system comprises one of the group consisting of AOL AIM Instant Messenger;

Microsoft MSN Messenger;

Yahoo! Messenger;

ICQ;

Jabber;

Groove; and

Sun JXTA.

5. A peer-to-peer communication system according to claim 1 wherein said browser and said broker comprise two distinct software programs.

6. A peer-to-peer communication system according to claim 1 wherein said broker is built into said browser.

7. A peer-to-peer communication system according to claim 1 wherein said broker comprises a browser plug-in.

8. A peer-to-peer communication system according to claim 1 wherein said browser and said broker reside on the same machine.

9. A peer-to-peer communication system according to claim 1 wherein the contents of said browser are represented in one of the group consisting of HTML;

XHTML;

XML; and

their variations.

10. A peer-to-peer communication system according to claim 9 wherein said first event message is an XML message.

11. A peer-to-peer communication system according to claim 9 wherein said second event message is an XML message.

12. A peer-to-peer communication system according to claim 9 wherein said first event message and said second event message are XML messages.

13. A peer-to-peer communication system according to claim 9 wherein said browser comprises Microsoft Internet Explorer (IE).

14. A peer-to-peer communication system according to claim 9 wherein said browser comprises one from the group consisting of Mozilla and its variants.

15. A peer-to-peer communication system according to claim 9 wherein said browser comprises Netscape Navigator.

16. A peer-to-peer communication system according to claim 1 wherein the contents of said browser are uniquely addressable by said broker using an established identification mechanism.

17. A peer-to-peer communication system according to claim 16 wherein the contents of said browser are uniquely addressable using the Document Object Model (DOM) defined by The World Wide Web Consortium (WC3).

18. A peer-to-peer communication system according to claim 16 wherein the contents of said browser are uniquely addressable using a stream-based HTML document model.

19. A peer-to-peer communication system according to claim 18 wherein the contents of the browser are uniquely addressable using a stream-based HTML document model with absolute character position.

20. A peer-to-peer communication system according to claim 16 wherein the contents of said browser are uniquely addressable using a DHTML model.

21. A peer-to-peer communication system according to claim 16 wherein said identification mechanism comprises one of the group consisting of an ID attribute for a DOM element in a browser;

an XPATH expression; and

XPointer expression;

an XLINK expression;

an Internet Explorer (IE) Markup Pointer identifying contents in a browser;

an absolute character position in a stream-based HTML document model; and

an object naming identification mechanism in a DHTML model.

22. A peer-to-peer communication system according to claim 21 wherein said identification mechanism comprises an XPointer expression, and further wherein said XPointer expression is constructed by walking backwards through the DOM tree until finding the earlier of the root or the ID attribute of a containing object.

23. A peer-to-peer communication system according to claim 21 wherein said XPointer expression is resolved by searching the DOM tree from the root of the sub tree to the final node of the XPointer path.

24. A peer-to-peer communication system according to claim 23 wherein the root of the subtree is an object ID or the root of the document.

25. A peer-to-peer communication system according to claim 1 wherein the browser-broker connection is implemented in one of the group consisting of the Component Object Model (COM);

and the Cross Platform Component Object Model (XPCOM).

26. A peer-to-peer communication system according to claim 1 wherein the browser-broker connection is implemented in one of the group consisting of HTTP;

XML-RPC; and

the Simple Object Access Protocol (SOAP).

27. A peer-to-peer communication system according to claim 1 wherein the contents of said browser comprise an embedded object.

28. A peer-to-peer communication system according to claim 27 wherein said embedded object exposes only a specific set of properties and procedures to its host.

29. A peer-to-peer communication system according to claim 28 wherein said embedded object comprises one of the group consisting of the Microsoft Media Player;

the Microsoft Visio ActiveX plug-in;

the Macromedia Flash Player ActiveX control;

the Macromedia Flash Player Java applet; and

the WildTangent Web Driver Java Plug-in for 3D graphics and games.

30. A peer-to-peer communication system according to claim 27 wherein said embedded object exposes its internal components, properties and procedures to its host.

31. A peer-to-peer communication system according to claim 30 wherein said embedded object comprises one of the group consisting of Mozilla'"'"'s support for MathML and SVG;

IE'"'"'s support for VML, HTML+TIME;

the Adobe SVGViewer plug-in; and

the Macromedia Flash Player implemented in IE'"'"'s behavior.

32. A peer-to-peer communication system according to claim 27 wherein said embedded object is configured to release said first event to said browser, whereupon said broker can monitor said first event, encode said first event in said first event message, and push said first event message to said at least on other peer.

33. A peer-to-peer communication system according to claim 27 wherein said second event message is configured so that said broker activates a specific set of properties and procedures of said embedded object.

34. A peer-to-peer communication system according to claim 27 wherein said second event message is configured so that said broker will repost said second event to said embedded object.

35. A peer-to-peer communication system according to claim 1 wherein only changes to a document are pushed to peers.

36. A peer-to-peer communication system according to claim 35 wherein said changes comprise content changes.

37. A peer-to-peer communication system according to claim 35 wherein said changes comprise style changes.

38. A peer-to-peer communication system according to claim 35 wherein said changes comprise view changes.

39. A peer-to-peer communication system according to claim 35 wherein said changes comprise navigation changes.

40. A peer-to-peer communication system according to claim 35 wherein said broker is configured so that when it pushes the results of said second event message to said browser, it marks the same to prevent re-transmission to the other peers.

41. A peer-to-peer communication system according to claim 1 wherein said second event message contains information regarding which peer originated said second event message.

42. A peer-to-peer communication system according to claim 41 wherein said broker is configured to take selective action according to which peer originated said second event message.

43. A peer-to-peer communication system according to claim 1 wherein said broker is configured to push the results to said browser so that said browser will utilize its script engine to respond to events and associated changes originated at other peers.

44. A peer-to-peer communication system according to claim 1 wherein concurrency control is maintained among the peers.

45. A peer-to-peer communication system according to claim 44 wherein concurrency control is maintained by using at least one of the group consisting of locks;

and timestamp ordering.

46. A peer-to-peer communication system according to claim 45 wherein said broker is configured so that said locks may be applied on the basis of one or more objects and/or portions of objects.

47. A peer-to-peer communication system according to claim 46 wherein said broker is configured so that said timestamp ordering accommodates changes to objects and/or portions of objects on multiple peers.

48. A peer-to-peer communication system according to claim 47 wherein said broker is configured so that said timestamp ordering comprises a base time synchronization and, for each change, a starting timestamp and an ending timestamp.

49. A peer-to-peer communication system according to claim 1 wherein said broker is configured to send a tool to said at least one another peer.

50. A peer-to-peer communication system according to claim 1 wherein said broker is configured to push a tool to said browser.

51. A peer-to-peer communication system according to claim 50 wherein said tool was received from said at least one other peer.

52. A peer-to-peer communication system according to claim 50 wherein said tool was resident with said broker.

53. A peer-to-peer communication system according to claim 50 wherein said broker is configured to request a tool from a peer.

54. A peer-to-peer communication system according to claim 53 wherein said broker is configured so that when it decodes said second event message, it will determine whether a non-resident tool is required and, if so, it will request the non-resident tool from the peer originating said second event message.

55. A peer-to-peer communication system according to claim 50 wherein said tool comprises at least one from the group consisting of scripts, style sheets, HTML/XHTML/XML contents and other special markups.

56. A peer-to-peer communication system according to claim 50 wherein said tool comprises at least one from the group consisting of an ActiveX control and a Java applet.

57. A peer-to-peer communication system according to claim 50 wherein said tool comprises a plug-in.

58. A peer-to-peer communication system according to claim 1 wherein said broker is configured to observe the screen position of said browser and to advise the at least one other peer of the same.

59. A peer-to-peer communication system according to claim 58 wherein said broker is configured to encode a position relative to the contents of said browser.

60. A peer-to-peer communication system according to claim 59 wherein said broker is configured to encode a position relative to a containing object.

61. A peer-to-peer communication system according to claim 60 wherein said broker is configured to encode a position relative to a containing object and the character position relative to the beginning or ending of that containing object.

62. A peer-to-peer communication system according to claim 61 wherein said broker is configured to determine the character position using a range object.

63. A peer-to-peer communication system according to claim 60 wherein said broker is configured to encode a position relative to a containing object and the relative proportional position within the containing object.

64. A peer-to-peer communication system according to claim 59 wherein said broker is configured to reflect the screen position on said browser using a range object.

65. A peer-to-peer communication system according to claim 1 wherein said broker is configured to receive the screen position of said at least one other peer and to reflect the same on its associated browser.

66. A method for operating a peer-to-peer communication system over an underlying computer network system, said method comprising:

(1) initiating a first event in a first browser;

(2) capturing the first event and associated changes with a first broker;

(3) encoding the first event and associated changes in a first event message;

(4) pushing the first event message to a second broker over the underlying computer network system;

(5) decoding the first event message into corresponding commands for recreating the first event and associated changes on a second browser; and

(6) pushing the corresponding commands to the second browser, whereby to recreate the changes associated with said second event on said second browser.

67. A method according to claim 66 wherein said underlying computer network system comprises an Instant Messenger (IM) system.

68. A method according to claim 66 wherein said first event message is encoded in XML.

69. A method according to claim 66 wherein object references for said first event are serialized in XPointer expressions.

70. A method according to claim 66 wherein the peer-to-peer dialogue is initiated with a blank Web page.

71. A method according to claim 66 wherein the peer-to-peer dialogue is initiated with an existing Web page.

72. A method according to claim 71 wherein the existing Web page originates at one of the peers, and the originating peer pushes the existing Web page to the other peers.

73. A method according to claim 71 wherein the existing Web page originates at a non-peer site, and all of peers obtain the existing Web page from that non-peer site.

74. A method according to claim 71 wherein the existing Web page originates at a non-peer site, one of the peers obtains the existing Web page from the non-peer site, and the obtaining peer pushes the existing Web page to the other peers.

75. A method according to claim 66 wherein, upon receiving said corresponding commands, the second broker causes the first broker to push a tool to the second browser.

76. A peer-to-peer communication system for use over an underlying computer network system, said peer-to-peer communication system comprising:

a broker interposed between a browser located on a peer and the underlying computer network system, with said broker being adapted to (1) monitor a first event taking place within said browser, encode said first event and associated changes in a first event message, and push said first event message to at least one other peer over the underlying computer network system, whereby said at least one other peer can reproduce on said at least one other peer the changes associated with the first event; and

(2) receive a second event message from said at least one other peer, where said second event message has been encoded to correspond to a second event and associated changes taking place on said at least one other peer, decode said second event message and push the results to said browser, whereby to recreate the changes associated with the second event within said browser.