Bossless architecture and digital cell technology for computer programs

• US 6,173,391 B1
• Filed: 02/18/1998
• Issued: 01/09/2001
• Est. Priority Date: 04/07/1995
• Status: Expired due to Fees

• Current Assignee: Sofmap Future Design Incorporated
• Original Assignee: Sofmap Future Design Incorporated
• Inventors: Nakajima, Ichiro, Tabuchi, Daisuke, Shoji, Wataru
• Primary Examiner(s): Coleman, Eric
• Application Number:
  US09/025,529
• Time in Patent Office: 1,056 Days
• Field of Search: 712/200, 712/205, 712/220, 709/108, 709/202
• US Class Current: 712/200
• CPC Class Codes: G06F 9/4484 Executing subprograms
• CPC Class Codes: G06F 9/45512 Command shells
• CPC Class Codes: G06F 9/543 User-generated data transfer, e.g. clipboards, dynamic data exchange [DDE], object linking and embedding [OLE]

Abstract

A bossless computer program architecture in which each program module is hierarchically equal is used to develop complicated software applications. Each program module is associated with a parameter file. The characteristics and operation of the program modules are determined by their associated parameter files. These modules communicate by writing statements to the parameter files associated with other modules. Once written, the origin of these statements is ignored. Thus, there is no need to “return” to the modules which originate the statements. Further, the statements are executed by the modules without regard to their origins. This new architecture does not require the preservation of linkage information because there is no need for the program modules to return information or control to other modules. Various applications of this architecture to windows-based environment and multimedia applications are disclosed.

Claims

1. A computing device for executing a software application, said software application comprising:

at least a first and a second software program modules each containing program instructions;

said second module containing program instructions for issuing a first set of one or more commands to said first module;

said first module containing program instructions for automatically executing said first set of commands without returning result of executing to said second module, said first module further containing program instructions for issuing a second set of one or more commands to said second module; and

said second module containing program instructions for automatically executing said second set of commands without returning result of executing to said first module.

2. The device of claim 1 wherein said first module further comprises program instructions for invoking a third program module, said third module executing its own program instructions without returning result of executing its program instructions to said first module.

3. The device of claim 2 wherein said first module can be terminated while said third module remains active.

4. The device of claim 3 wherein said third module can issue a command causing said first module to be terminated.

5. The device of claim 1 wherein said first and said second sets of commands do not contain information on their origins.

6. A computing device for executing a software application, said software application comprising:

at least a first and a second software program module, each of said modules containing program instructions and being associated with a separate file capable of accepting statements from other modules;

said second module containing program instructions for sending a first set of one or more statements to a first file associated with said first module;

said first module containing program instructions for automatically executing said first set of statements without returning result of executing said first set of statements to said second module, said first module further containing program instructions for sending a second set of one or more statements to a second file associated with said second module; and

said second module containing program instructions for automatically executing said second set of statements without returning result of execution to said first module.

7. The first file of claim 6 comprising:

a first section for receiving statements sent by other modules, and

a second section containing indicia of status of said first file, said second module examining said indicia prior to sending said first set of statements.

8. The first file of claim 7 wherein said second section contains a first pointer associated with one of said statements in said first file, said first pointer being changeable for reflecting addition of said first set of statements to said first file.

9. The first file of claim 8 wherein said second section further contains a second pointer pointing to a statement in said first file currently being executed by said first module.

10. The first file of claim 7 wherein said indicia has at least a first status and a second status, said first status indicating that said first file is ready to accept new statements and said second status indicating that said first file is not able to accept new statements.

11. The first file of claim 7 further comprising a set of parameters relating to characteristics of said first module, said first module containing program instructions for using said parameters when said first module is invoked.

12. A method for interacting at least two software program modules included in a software application in a computing device, each of said modules containing program instructions and being associated with a separate file, comprising the steps of:

sending a first set of one or more statements by a second module to a first file associated with a first module; and

executing, by said first module, said first set of statements automatically without returning result of executing said first set of statements to said second module.

13. The method of claim 12 further comprising the steps of:

sending a second set of one or more statements by a third module to said first file subsequent to said first sending step; and

executing, by said first module, said second set of statements automatically without returning result of executing said second set of statements to said third module, said second set of statements being executed subsequent to completion of said step of executing said first set of statements.

14. The method of claim 13 wherein said second sending step is initiated prior to completion of said step of executing said first set of statements.

15. The method of claim 12 wherein said step of sending said first set of statements comprises the steps of:

examining a section of said first file containing status information; and

sending said first set of statements when said first file is in a status capable of accepting said first set of statements.

16. A computer program product having a software application, said software application comprising:

at least a first and a second software program modules each containing program instructions;

said second module containing program instructions for issuing a first set of one or more commands to said first module;

said first module containing program instructions for automatically executing said first set of commands without returning result of executing to said second module, said first module further containing program instructions for issuing a second set of one or more commands to said second module; and

said second module containing program instructions for automatically executing said second set of commands without returning result of executing to said first module.

17. A computer program product having a software application, said software application comprising:

at least a first and a second software program module, each of said modules containing program instructions and being associated with a separate file capable of accepting statements from other modules;

said second module containing program instructions for sending a first set of one or more statements to a first file associated with said first module;

said first module containing program instructions for automatically executing said first set of statements without returning result of executing said first set of statements to said second module, said first module further containing program instructions for sending a second set of one or more statements to a second file associated with said second module; and

said second module containing program instructions for automatically executing said second set of statements without returning result of execution to said first module.