The present invention relates in general to digital processing, and in particular to a system allowing computing environments to be treated as electronic documents or as software programs and to a set of services based on the system.
Although the software components of a computer—the operating system and the set of applications running on top of it—abstractly determine the notion of a “computing environment,” in today's practice this notion is closely tied to the underlying hardware as well. Thus, for instance, computer A is considered to be a Windows NT desktop, while computer B is considered to be a Linux server, and computer C a Windows 98 laptop. The bewildering variety of hardware devices reinforces this notion.
Furthermore, the notion of a computing environment can be extended, without loss of generality, to a collection of systems connected by a network. Again, in today's practice, this extended notion carries with it a close association to the underlying hardware, in particular to the individual computers' hardware and the networking hardware used for connecting these computers. For instance, a user connecting a laptop computer to a local area network may need to be aware of the vendor and type of the network card used.
This tight coupling between a computing environment and the underlying hardware, with the added complexity of a networked system, introduces a host of avoidable—yet presently insurmountable—issues to be dealt with by any user intending to buy, provide or use a computing environment.
For instance, an organization may decide to locate a computer in a conference room shared by the marketing and the engineering departments of the organization. The marketing department uses the computer for slide shows and requires the environment of the computer to include Microsoft Windows NT operating system and PowerPoint software. The engineering department uses the computer for product demonstrations and requires the environment to include Linux operating system. With prior art, the computer can provide one environment or the other but cannot readily be changed from one environment to another. The users are usually interested in their specific environments, not their specific computers.
As another example, a system administrator of an organization may be assigned to provide technical support for all computer users within the organization. If the system administrator needs to fix a problem in a user's computing environment, he/she needs to physically visit the user's location. Using prior art, there is no possible way for the administrator to transfer the user's environment to—or replicate the user's environment at—the administrator's location.
Thus, it is desirable to provide a system that decouples computing environments from the hardware as much as possible. Such a system will permit computing environments to be handled as abstractions, which are—at least partially—agnostic about hardware. Services based on such a system will provide increased flexibility for users and reduced maintenance for administrators. Thus the systems and services will be advantageous over prior art in improving the cost-benefit ratio of computing environments.
A system for describing computing environments as electronic documents, programs or other types of electronic representation or data. The environment description can be easily created, transferred and ultimately used to create the specified environment for use by an end user, or users, in many different applications.
One feature of the invention provides abstraction software and a user interface to allow a human user to specify a definition for the computing environment. Desired components are selected and included in the environment definition. Default components can be provided to help a user design a viable environment. Hardware and software components can also be associated with constraints so that, for example, incompatible components such as software that can not run on different central processing units, under certain operating systems, etc., will not be selected. Abstraction software can also use parameters to associate additional qualities, restrictions or properties with components.
Environment definitions can be stored and transferred in a manner compatible with typical electronic information. Copies of definitions can be made. Definitions can be viewed by application programs, browsers, etc. Definitions can be edited by users with similar types of software, or with other, dedicated software.
Environment definitions can be installed onto hardware and software resources by installation software. Environments can be installed on specific components from which the environment was originally abstracted, or on other sufficiently similar components. Environments can be remotely manipulated and accessed from computers, terminals, web browsers, handheld devices, or other devices. Various services can be provided, or implemented, with the system of the present invention. Examples of services include allowing interactive selection and loading of environments, uploading previously saved environments for storage and future use, replicating environments and distributing the environments as for a corporate-wide deployment in several countries, etc.
Other advantages of the invention are described, including business models such as where a service provider can ensure reliability by having backups of environments that can be easily recalled and reinstated; data center management is facilitated; remote access of environments is made more efficient; and other benefits are achieved.
In one embodiment the invention provides a method for creating an electronic document description of a computing environment installed on computing hardware. The method includes identifying at least one software component of the computing environment; and automatically generating an electronic document containing an identification of each of the at least one software component, the electronic document comprising instructions for automatically reconstructing the computing environment on first computing hardware or on other computing hardware.
In another embodiment the invention provides a method for installing a computing environment on target computing hardware based on an electronic document description of the computing environment. The method includes obtaining an electronic document that contains a description of a computing environment to be installed; reading the electronic document; identifying candidate computing hardware for installation of the computing environment; selecting target computing hardware from the candidate computing hardware for installation of the computing environment; and installing at least one software component on the target computing hardware in accordance with data contained in the electronic document.
In the description herein, the term “computing environment” (or simply “environment”) includes an operating system and all the applications and documents installed on top of it, or a collection of networked computing environments.
An example of a computing environment is shown in
The present invention provides a system and method for abstracting environments as documents or programs, as well as a system and method for installing environments abstracted as documents or programs on compatible hardware. The system of the present invention can be used to support a number of business models, as the following description will make clear.
The terms “document” and “program” are used interchangeably herein. As will be evident from this disclosure, the present invention handles environments as documents in the sense that they can be stored, copied, edited, etc. But, as will also be evident from this disclosure, environment “documents” may be run or installed in the manner of programs.
Abstracting Environments as Documents or Programs
With the present invention a computing environment may be abstracted out as an electronic document or a computer program.
For example, the environment shown in
Alternatively, in step 401a user may also specify an environment without having access to the components. In this situation, a number of environments must have already been abstracted from hardware and stored either on local storage 312 or at remote facility 330. The user selects from these environments a number of components to be included in the user's environment; the user may also accept a default environment defined by a service provider and stored at remote facility 330. As with the abstracting process, the user preferably uses a visual interface to select components.
Once the user has identified the components, in step 402 the abstracting software builds an environment document or environment program incorporating these components. An environment document or environment program may be pure binary code; however, top-level structure may be represented in any language that enables hierarchical data representations. A preferred embodiment uses XML as a data representation language for the top-level structure.
Although one purpose of abstracting computing environments as documents according to the present invention is to abstract away from specifics of the hardware, some abstracted computing environments may still have dependencies on the hardware. For example, in the environment shown in
Those skilled in the art will appreciate that this technique can be used to include constraints regarding any aspect of the environment, not just hardware; for instance, some versions of software application programs can not run under certain operating systems, or with certain versions of operating systems. Thus, an operating system can have constraints of certain types and versions of application programs, and vice versa.
In a preferred embodiment, the process of abstraction optionally may include abstracting a set of parameters from the environment. Parameters may include specifics of the operating system (genre, version etc.), specifics of the application software (kinds, versions etc.), or the footprints of the application software (installation directories, configuration files etc.).
Parameters may also include sets of possible parameters i.e., types. In such cases, the environment document or environment program created in step 402 may act as a template for different possible environments. For example, in the environment of
Transmission and Replication of Environments
In step 404, the environment program is stored. The program may be stored locally, for instance, in local storage 312 of
The document or program may also be replicated to create multiple copies of the same environment. Procedures for replicating (copying) electronic documents are well known in the art.
The document or program may also be edited to modify the environment. There are two different approaches to modifying environment documents. In a preferred embodiment, the user installs an environment on hardware, modifies one or more components of the environment (e.g., adding a new web server in
In an alternative embodiment, a user edits the document directly. For instance, in the document shown in
Installing Environments
In an embodiment of the present invention, an environment program may be installed either on the hardware from which the environment was abstracted or on other sufficiently similar hardware.
A user uses a terminal 510 to communicate with server 530 in order to configure environments on hardware 540. In a preferred embodiment, user communication with server 530 is via a secured socket layer (SSL) such as layer 521. Hardware 540 may also have its own connection to Internet 520, independent of server 530, preferably via SSL 545, to enable user communication with installed environments.
Environment storage is provided by RAID arrays 624, 626, 632, and 634. RAID arrays 624 and 626 communicate with server farm 614 via storage host CPUs 622 to provide “clean configurations.” Clean configurations are environments supported by the service provider that can be provided by replication to different users. RAID arrays 632 and 634 communicate with server farm 614 via configuration host CPUs 630 to provide “dirty configurations.” Dirty configurations are environments specified by users by editing or modifying clean configurations. These environments are specific to users and may not be used by others. Separating clean from dirty configurations provides protection for users' privacy and a measure of security for the service provider.
The hardware for installing environments includes a plurality of user Linux boxes 636 and a plurality of user Win boxes 638. NIS/DNS server farm 640 and Ethernet switch 628 are provided to support networked environments, such as the environment of
In a preferred embodiment, users may also communicate with installed environments on Linux boxes 636 and/or Win boxes 638. VNC viewers running on Linux boxes 636 and Win boxes 638 enable this communication. SSL 604 provides a secure channel. The selection and interconnection of these devices, along with other degrees of control of these devices, allows a user to set up many sizes and types of processing architectures and environments.
It is possible to use widely-varying components, or resources, other than those shown in
An example installation process using the embodiment of
Next, in step 702, an instruction to install an environment program is received at server 530; this step may involve a user sending an environment program for installation to the server via a network or instructing the installer to retrieve and install an environment program from local storage 535. If the environment program was transformed for transfer and/or storage, the installation process performs a reversal of the transformation(s) in step 703.
The installation process then selects hardware on which to install the environment (step 704) and installs the specified applications and documents on that hardware (step 705). As noted above with respect to
According to the present invention, it is guaranteed either that the environment can be recovered identically to the saved form or that the environment can be recovered in a form that is “behaviorally equivalent” to the saved form. The “behavioral equivalence” of two environments will be pre-defined for each operating system, for each application within an operating system, and inductively for each combination of applications within an operating system.
For instance, consider Apache web server 1 and Apache web server 2 (out of the 100) in
In a preferred embodiment, an environment program may include hardware constraints as described above. In such a case, in step 704 the installation process selects “compatible hardware,” i.e., any hardware “box” that satisfies all of the constraints of the environment program. To determine whether a computing environment can be installed on a given hardware box, the installation process needs only to establish that the given hardware is compatible hardware for the computing environment. For instance, if an environment has a constraint set given by the expression:
A process for selecting compatible hardware in step 704 is shown in
In other words, to the installation process, symbolic constraint variables such as “Arch” or “Memory” are nothing but names. It is therefore possible to build up arbitrarily complicated sets of constraints without having to incorporate machine-specific checks in the installation process.
Additionally, in a preferred embodiment the environment program may be a template for different possible environments, as described above. In this case, the installation process is preceded by an instantiation process, which specifies values for the parameters. An example instantiation process is shown in
If the environment program is a template, the installer determines parameter values in step 902 and creates an instance of the program with the appropriate values in step 903. For example, suppose that the template environment is C(WinNT_version). The process of instantiation will determine an available version of Windows NT (e.g., 4.0) by consulting a database of available software/OS and create an instance C_WinNT—4.0. This instance is an environment program, since the only parameter has been defined. If there are multiple parameters, steps 902 and 903 are repeated until all parameters have been defined. The instantiated program is then used in the remaining installation steps, beginning with step 704.
Remote Manipulation of Environments
As described above with respect to
In a further embodiment, environments may be stored remotely and installed after transferring over the network into local hardware. The installation process can be initiated by either side—by push or by pull. For example, in the system of
Other embodiments include remote access to installed environments and remote installation of environments. In the embodiment of
Services
The foregoing systems and methods for handling computing environments as documents make possible a set of “externalization” services whereby a user interacts with a service provider via a network to create, replicate, store, and install environments. For purposes of such services, a system like that shown in
Some services will be apparent to one skilled in the art based on the foregoing disclosure. For instance, one service enables a user to interactively select an environment to be downloaded to a local machine or local network. The user may then save the selected environment for future use or install it and use it. Another service enables a user to upload a previously saved environment onto compatible hardware provided by a service provider or to a storage area provided by the service provider. Still another service enables a user to replicate an environment and to install multiple copies of the environment.
Additional services can be provided based on the systems and methods disclosed above. One skilled in the art will be able to see that these systems and methods can provide, among others, the following services:
One service enables a user to edit an environment to add, remove, or replace application software supported and/or licensed by the service provider. The service provider handles the provisioning of licenses and usage rights associated with the application software.
Another service enables a user to invoke application-deployment software provided by the service provider to add, remove, or replace application software not supported or licensed by the service provider, herein referred to as third-party software. This feature may be handled by the installer process described above with regard to
Another service enables a user to edit a program to add, remove, or replace data associated with the applications that are components of an environment.
Business Models
Using the system and method of the present invention enables a number of business models. For example, a service provider can provide reliable, fault-tolerant computing environments. In this model, the service provider automatically makes a copy of the user's computing environment. If the user's environment is destroyed, the user is able to retrieve it from the service provider. Conversely, at regular intervals, the user may back up the environment with the service provider. If the user's hardware becomes damaged in some way, the service provider can quickly provide the user's environment to replacement hardware.
As a second example, a service provider can provide high-capacity, scalable computing environments referred to as “data centers” or “network operation centers” (NOCs). These centers are large centralized locations that provide computing infrastructure (hardware, software and networking) to organizations. One embodiment of the present invention enables NOCs to easily accommodate dynamically changing needs of organizations. For instance, an organization may use a first network for its e-commerce operations, a second network for its internal operations, and a third network for its information web site. The e-commerce operation may need more resources during the Christmas shopping season, while the information web site may be doing webcasts of football games, leading to a need for extra resources on game days. So the resource requirements grow and shrink dynamically; for instance, the information web site may need 100 web servers on a “normal” day but 300 on game days. In an NOC using prior art systems, installing a new environment (e.g., converting a hardware box from the information web site configuration to the e-commerce configuration) typically takes days since installation is done manually, and frequent (e.g., every other day) repetition of an installation is not feasible. Using the present invention, a NOC provider may enable users to change environments installed on machines at the touch of a button. Thus the present invention makes environments scalable both in space and time (more machines in less time).
As a further example, a service provider may also provide mobile environments. The service provider provides a collection of hardware that the user can access remotely, for instance through the World Wide Web or via a cell phone or personal digital assistant (PDA). This allows the user to access the environment virtually anywhere. Conversely, the environment may be copied to the user's system (e.g., local desktop, laptop, or PDA and occasionally backed up to the service provider's databases. This provides the user the same benefits as a remote environment without the costs of accessing the environment remotely. Moreover, mobile-environment users who want to use different environments at different times need not “carry” all the environments around; they can simply swap environments in and out on the same hardware (local or remote). For example, a software engineer may develop products using Linux, Java, Apache and emacs, and draft documents using Windows and Microsoft Word. Using the mobile environment service, this engineer can “carry” either one of the environments on his laptop and quickly swap environments on the same laptop by accessing the service provider.
As a further example, a service provider may also provide tailored environments, also called Application Specific Environments (ASE). The service provider provides complete environments for particular problem-domains, such as an application-server environment, an inventory-management environment, and so on. Environments may also be created to cater to certain categories of users, for example, executives, accountants, designers and engineers For example, a standard Software Engineer's environment may include Linux OS; compilers for Java, C, and Peri (or other languages); editors; testing tools; and performance tools. A standard furniture designer's environment may include Windows OS, Microsoft Office (for documentation, project scheduling, etc.), 3-D visualization software for designs, and high-quality printing software. The service provider, instead of the user, handles installation and licensing issues for setting up these environments.
As a further example, a service provider may also provide low maintenance environments, also called outsourced computing. In this model, the service provider owns the hardware and provides remote access to users. This offers users a number of advantages. For example, the service provides easy software installation services and update/patch services on a large scale (by replication). In addition, troubleshooting errors becomes simpler because of the ability to replicate an environment. For instance, intrusive/destructive testing can be performed on a replication of the troubled system while the system itself remains in use, without affecting the functionality or performance of the system. Replication also allows multiple tests to be performed in parallel on different copies of the system, thereby speeding up troubleshooting.
Further, users can compare and evaluate different environments without large overhead costs in procuring, installing and maintaining the hardware and software over short periods of time. Still further, the service provider can provide versioning services for an environment—automatic check-pointing and saving at different states along with roll back.
With the novel systems and methods provided by the present invention, a machine no longer needs to run a particular computing environment, nor does a particular computing environment need to run on a particular machine. A user chooses which computing environment to run. When the user's needs change, the computing environment is easily swappable for another one. Similarly, the user is not limited to running a particular computing environment on a particular machine as computing environments can be readily transferred from one machine to another. For example, a user can move an environment from a PC at home to a laptop, or place the environment in a centralized server that can be accessed from anywhere on the Internet.
These features are brought about by providing an electronic document description of the environment and having a configuration system capable of automatically configuring resources in accordance with the environment's document description. Multiple copies of environments can be made and provided to others. Application vendors can provide entire computing environments to their customers, greatly easing installation issues. Additionally, environments can be modified. One can easily customize an environment for one's own purpose.
Although the present invention has been discussed with respect to specific embodiments, these embodiments are merely illustrative, and not restrictive, of the invention. For example, as used herein, the term “electronic document” should be construed to include information that can be displayed to a human user as well as information that can be read or processed by hardware or software. A “software program” includes instructions or symbols that can be read or interpreted to direct functional actions in software or hardware. The terms “electronic document,” “document,” “software program” and “program” are each intended to broadly refer to any form of information, including physical and electronic representations. Thus, the scope of the invention is to be determined solely by the appended claims.
This application is a continuation of U.S. patent application Ser. No. 09/872,346, entitled “System And Services For Handling Computing Environments As Documents,” filed Jun. 1, 2001 now U.S. Pat. No. 7,043,724, naming William Blume, Sekaran Nanja and Jagadish Bandhole as inventors, which claims priority from U.S. Provisional Application No. 60/232,602, filed Sep. 14, 2000, entitled “A System for Handling Computing Environments as Documents or as Programs and a Set of Services Based on the System,” and is also related to U.S. patent application Ser. Nos. 09/663,252 and 09/662,990, entitled “User Interface for Dynamic Computing Environments Using Allocable Resources” and “System for Configuration of Dynamic Computing Environment Using a Visual Interface,” filed Sep. 15, 2000. All of the aforementioned applications and their disclosures are incorporated herein by reference for all purposes as if completely and fully set forth herein.
Number | Name | Date | Kind |
---|---|---|---|
4925311 | Neches et al. | May 1990 | A |
5191611 | Lang | Mar 1993 | A |
5394522 | Sanchez-Frank et al. | Feb 1995 | A |
5410707 | Bell | Apr 1995 | A |
5418918 | Vander Kamp et al. | May 1995 | A |
5421009 | Platt | May 1995 | A |
5452454 | Basu | Sep 1995 | A |
5463766 | Schieve et al. | Oct 1995 | A |
5479599 | Rockwell et al. | Dec 1995 | A |
5515524 | Lynch et al. | May 1996 | A |
5555370 | Li et al. | Sep 1996 | A |
5577210 | Abdous et al. | Nov 1996 | A |
5668995 | Bhat | Sep 1997 | A |
5694600 | Khenson et al. | Dec 1997 | A |
5727213 | Vander Kamp et al. | Mar 1998 | A |
5752041 | Fosdick | May 1998 | A |
5802290 | Casselman | Sep 1998 | A |
5842011 | Basu | Nov 1998 | A |
5864699 | Merryman | Jan 1999 | A |
5894571 | O'Connor | Apr 1999 | A |
5942738 | Cesaire et al. | Aug 1999 | A |
5948101 | David et al. | Sep 1999 | A |
5974443 | Jeske | Oct 1999 | A |
5974547 | Klimenko | Oct 1999 | A |
6002871 | Duggan et al. | Dec 1999 | A |
6009507 | Brooks et al. | Dec 1999 | A |
6058113 | Chang | May 2000 | A |
6081846 | Hyder et al. | Jun 2000 | A |
6081864 | Lowe et al. | Jun 2000 | A |
6085318 | Vander Kamp et al. | Jul 2000 | A |
6092189 | Fisher et al. | Jul 2000 | A |
6098067 | Erickson | Aug 2000 | A |
6101601 | Matthews et al. | Aug 2000 | A |
6122738 | Millard | Sep 2000 | A |
6182123 | Filepp et al. | Jan 2001 | B1 |
6182275 | Beelitz et al. | Jan 2001 | B1 |
6189100 | Barr et al. | Feb 2001 | B1 |
6192518 | Neal | Feb 2001 | B1 |
6202091 | Godse | Mar 2001 | B1 |
6230200 | Forecast et al. | May 2001 | B1 |
6259448 | McNally et al. | Jul 2001 | B1 |
6262726 | Stedman et al. | Jul 2001 | B1 |
6266678 | McDevitt et al. | Jul 2001 | B1 |
6282709 | Reha et al. | Aug 2001 | B1 |
6298443 | Colligan et al. | Oct 2001 | B1 |
6304965 | Rickey | Oct 2001 | B1 |
6308238 | Smith et al. | Oct 2001 | B1 |
6370560 | Robertazzi et al. | Apr 2002 | B1 |
6374336 | Peters et al. | Apr 2002 | B1 |
6393557 | Guthridge et al. | May 2002 | B1 |
6421777 | Pierre-Louis et al. | Jul 2002 | B1 |
6446126 | Huang et al. | Sep 2002 | B1 |
6463530 | Sposato | Oct 2002 | B1 |
6466972 | Paul et al. | Oct 2002 | B1 |
6466978 | Mukherjee et al. | Oct 2002 | B1 |
6477624 | Kedem et al. | Nov 2002 | B1 |
6490564 | Dodrill et al. | Dec 2002 | B1 |
6493679 | Rappaport et al. | Dec 2002 | B1 |
6498791 | Pickett et al. | Dec 2002 | B2 |
6512526 | McGlothlin et al. | Jan 2003 | B1 |
6539456 | Stewart | Mar 2003 | B2 |
6543047 | Vrhel, Jr. et al. | Apr 2003 | B1 |
6550006 | Khanna | Apr 2003 | B1 |
6560606 | Young | May 2003 | B1 |
6564112 | Factor | May 2003 | B1 |
6577229 | Bonneau et al. | Jun 2003 | B1 |
6578076 | Putzolu | Jun 2003 | B1 |
6578141 | Kelley et al. | Jun 2003 | B2 |
6598131 | Kedem et al. | Jul 2003 | B2 |
6601095 | Duffield et al. | Jul 2003 | B1 |
6601166 | Ayyar et al. | Jul 2003 | B1 |
6604238 | Lim et al. | Aug 2003 | B1 |
6615365 | Jenevein et al. | Sep 2003 | B1 |
6633916 | Kauffman | Oct 2003 | B2 |
6662267 | Stewart | Dec 2003 | B2 |
6684327 | Anand et al. | Jan 2004 | B1 |
6711688 | Hubacher et al. | Mar 2004 | B1 |
6748525 | Hubacher et al. | Jun 2004 | B1 |
6751662 | Natarajan et al. | Jun 2004 | B1 |
6757837 | Platt et al. | Jun 2004 | B1 |
6768901 | Osborn et al. | Jul 2004 | B1 |
6802062 | Oyamada et al. | Oct 2004 | B1 |
6804774 | Larvoire et al. | Oct 2004 | B1 |
6810478 | Anand et al. | Oct 2004 | B1 |
7058700 | Casalaina | Jun 2006 | B1 |
7065637 | Nanja | Jun 2006 | B1 |
7082521 | Nanja | Jul 2006 | B1 |
20010011304 | Wesinger, Jr. et al. | Aug 2001 | A1 |
20020069369 | Tremain | Jun 2002 | A1 |
20020172222 | Ullmann et al. | Nov 2002 | A1 |
20030009552 | Benfield et al. | Jan 2003 | A1 |
20030046529 | Loison et al. | Mar 2003 | A1 |
20040054780 | Romero | Mar 2004 | A1 |
20050021723 | Saperia | Jan 2005 | A1 |
20050188088 | Fellenstein et al. | Aug 2005 | A1 |
Number | Date | Country |
---|---|---|
745929 | Apr 1996 | EP |
0 745 929 | Dec 1996 | EP |
841616 | May 1998 | EP |
Entry |
---|
Fabio Kon et al., “Dependence Management in Compnent-Based Distributed Systems”, Mar. 2000, pp. 26-36. |
Debenham, Clive, “Taos: The Operating System,” May 29, 1995, Tantric Technologies, Newsgroups: comp.parallel. |
Web Component, Using the Web Component, Copyright © 1997, Template Software, Inc. |
Simon—“Computer System Built to Order”—Nov. 25, 1996—Newsgroups: demon.adverts, midlands.adverts, sanet.adverts, solent.forsale, uk.adverts.computer, unet.adverts, uk.adverts.other, dungeon.forsale. |
Huang, Peter, California Polytechnic State University Design and Implementation of the CiNIC Software Architecture on a Windows Host, Feb. 2001, pp. i-87, http://www.ee.calpoly.edu/3comproject/masters-thesis/Huana-Peter.pdf. |
Henry, Mike, Intel Corporation, Extending PXE to Mobile Platforms, Jun. 1998, pp. 1-4, http://www.intel.com/update/archive/psn/psn06985.pdf. |
International Search Report as mailed from the PCT on Aug. 13, 2004 for WO Application (PCT/US03/28820; Filed Sep. 10, 2003), 3 pages). |
Template Software's Application Developer's Training Course, SNAP 8.0 Module 7, 1997. |
Workflow Template, Developing a WFT Workflow System, Whole manual, 1998. |
Workflow Template, Using the WFT Development Environment, Whole manual, 1998. |
Workflow Template, Using the Web Component, Whole manual, 1998. |
Clive Debenham, “Taos: The operating system,” Mar. 1995, Newsgroups: comp.parallel, pp. 1-8. |
Number | Date | Country | |
---|---|---|---|
60232602 | Sep 2000 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09872346 | Jun 2001 | US |
Child | 11430212 | US |