High-level adaptable bidirectional protocol for use between a hypermedia system and a plurality of editors

• US 5,537,546 A
• Filed: 10/23/1995
• Issued: 07/16/1996
• Est. Priority Date: 04/17/1992
• Status: Expired due to Fees

• Current Assignee: Bull Sas (Atos SE)
• Original Assignee: Bull Sas (Atos SE)
• Inventors: Sauter, Louis
• Primary Examiner(s): Ellis, Richard L.
• Application Number:
  US08/546,623
• Time in Patent Office: 267 Days
• Field of Search: 395/153, 395/154, 395/200.01, 395/200.04
• US Class Current: 709/230
• CPC Class Codes: G06F 16/748 Hypervideo linking data to content, e.g. by linking an URL to a video object in the context of video distribution systems H04N21/858
• CPC Class Codes: G06F 16/94 Hypermedia Hyperlinking G06F40/134
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/26 Special purpose or proprietary protocols or architectures network applications for proprietary or special purpose networking environments H04L67/12
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A very high-level bidirectional protocol (CP) used for communication between a hypermedia system (HS) and a large number of interconnected editors (HSE, Ea, Eb, Ec, . . . ) communicating within a hyperstructure. This protocol (CP) uses a set of messages that allow each editor to manipulate and manage the contents of hypermedia objects called nodes, and it is also manipulated by the hypermedia objects and is accessible through a programming interface.

Claims

1. A very high-level, adaptable bidirectional protocol for communication between a hypermedia system and a plurality of editors communicating within a hyperstructure, said protocol including a plurality of messages including open node and close node request messages sent by said hypermedia system when an action is to be executed by at least one of said editors, response messages sent by at least one of said editors in response to said request messages, event messages sent by at least one of said editors to inform said hypermedia system that various events have occurred, menu messages sent by at least one of said editors to inform said hypermedia system that a user has selected a predefined message and error messages sent by at least one of said editors when an error appears, said plurality of messages allowing each of said editors to manipulate and manage contents of hypermedia objects called nodes, while said protocol is manipulated by the hypermedia objects and is accessible through a programming interface, said nodes containing structures with an editor name for use with corresponding documents, said editors offering support for the protocol including said open node request and said close node request, whereby new editors may be easily integrated into an existing hyperstructure.

2. The protocol according to claim 1, wherein said protocol is based on a TCP/IP-type transmission management protocol.

3. The protocol according to claim 1 or 2, wherein said request messages of said protocol include

both a request and a connection number specific to said request, said request message specifying application context, editor name, editor function and number of connections supported by said editor, whereby a connection specified by said connection number is used for response and error messages corresponding to said request.

4. The protocol according to claim 3, wherein a sensitive zone in a node which corresponds to a multimedia document is created according to the following steps:

marking an area in a document that is selected as said sensitive zone;

sending said hypermedia system a menu message to create an anchor which is a hypermedia object representing said sensitive zone of said contents of said node;

creating said anchor and sending one of said editors a create anchor request message;

updating one of said editors to include said anchor that has been created.

5. The protocol according to claim 4, wherein said hypermedia system creates said anchor without direct user intervention by:

creating said anchor and sending one of said editors said create anchor request message; and

updating one of said editors to include said anchor that has been created.

6. The protocol according to claim 3, wherein an anchor, which is a hypermedia object representing a sensitive zone of the contents of a node, is deleted according to the following steps:

selecting said sensitive zone to delete;

sending said hypermedia system a delete anchor menu message;

deleting said anchor and sending at least one of said editors a delete anchor request message; and

deleting said hypermedia object from a document that corresponds to said anchor.

7. The protocol according to claim 6, wherein said hypermedia system deletes said anchor without direct user intervention by:

deleting said anchor and sending at least one of said editors a delete anchor request message; and

deleting said hypermedia object from said document that corresponds to said anchor.