Abstract: Systems and methods for software automation are provided. Software testcases are distributed across multiple data processing systems (equivalently, “machines” or “hosts”) that may collectively include multiple platforms (equivalently, “operating systems”). A testcase may be executed as one or more processes progressing through a sequence of phases, with execution within a phase being asynchronous among processes. Synchronization of the testcase processes across the data processing systems and platforms may be effected by managing an event; the testcase processes block on the event upon completion of the current testcase phase. A testcase phase execution service on each host handles synchronization events. The definition of the testcase may include metadata that identifies the particular phases in sequence, that is phase names, for the testcase; the phase names identifies the phases to the synchronization process that triggers the synchronization events which initiate each succeeding phase of the testcase.

Abstract: Systems and methods for software automation are provided. Software testcases are distributed across multiple data processing systems (equivalently, “machines” or “hosts”) that may collectively include multiple platforms (equivalently, “operating systems”). A testcase may be executed as one or more processes progressing through a sequence of phases, with execution within a phase being asynchronous among processes. Synchronization of the testcase processes across the data processing systems and platforms may be effected by managing an event; the testcase processes block on the event upon completion of the current testcase phase. A testcase phase execution service on each host handles synchronization events. The definition of the testcase may include metadata that identifies the particular phases in sequence, that is phase names, for the testcase; the phase names identifies the phases to the synchronization process that triggers the synchronization events which initiate each succeeding phase of the testcase.

Abstract: Systems and methods for software automation are provided. Software testcases are distributed across multiple data processing systems (equivalently, “machines” or “hosts”) that may collectively include multiple platforms (equivalently, “operating systems”). A testcase may be executed as one or more processes progressing through a sequence of phases, with execution within a phase being asynchronous among processes. Synchronization of the testcase processes across the data processing systems and platforms may be effected by managing an event; the testcase processes block on the event upon completion of the current testcase phase. A testcase phase execution service on each host handles synchronization events. The definition of the testcase may include metadata that identifies the particular phases in sequence, that is phase names, for the testcase; the phase names identifies the phases to the synchronization process that triggers the synchronization events which initiate each succeeding phase of the testcase.

Abstract: Systems and methods for software automation are provided. Software testcases are distributed across multiple data processing systems (equivalently, “machines” or “hosts”) that may collectively include multiple platforms (equivalently, “operating systems”). A testcase may be executed as one or more processes progressing through a sequence of phases, with execution within a phase being asynchronous among processes. Synchronization of the testcase processes across the data processing systems and platforms may be effected by managing an event; the testcase processes block on the event upon completion of the current testcase phase. A testcase phase execution service on each host handles synchronization events. The definition of the testcase may include metadata that identifies the particular phases in sequence, that is phase names, for the testcase; the phase names identifies the phases to the synchronization process that triggers the synchronization events which initiate each succeeding phase of the testcase.

Abstract: A client receives a response to a request from a client to a server to extract files from a software package. The reply includes an archive file of the files and attribute information for the files. The files and the attribute information are extracted from the archive file. The client determines that at least one of the files is associated with a first encoding different than a second encoding of the client. With the attribute information, the client determines that the at least one of the files is not a binary file. The client translates the at least one file from the first encoding to the second encoding.

Abstract: A mechanism for sharing files, and sets of related files, or packages of files, in a multi-host, multi-platform environment is provided. A public package client handles user requests to perform operations on a software package. Additionally, information about the package and the files contained therein may be obtained. A server, responsive to the client, performs the operations on the package. Data about the files is set in a data structure which may be stored in an archive along with the files themselves. In particular, this data may identify each file as either a text or binary file and as an executable file. A client may access the aforementioned data to determine if the file or files require further processing to adapt the file to the operating system on the client. Such processing may, for example, include linefeed/carriage return translation and codepage translation, or setting file attributes.

Abstract: Systems and methods for software automation are provided. Software testcases are distributed across multiple data processing systems (equivalently, “machines” or “hosts”) that may collectively include multiple platforms (equivalently, “operating systems”). A testcase may be executed as one or more processes progressing through a sequence of phases, with execution within a phase being asynchronous among processes. Synchronization of the testcase processes across the data processing systems and platforms may be effected by managing an event; the testcase processes block on the event upon completion of the current testcase phase. A testcase phase execution service on each host handles synchronization events. The definition of the testcase may include metadata that identifies the particular phases in sequence, that is phase names, for the testcase; the phase names identifies the phases to the synchronization process that triggers the synchronization events which initiate each succeeding phase of the testcase.

Abstract: A mechanism for sharing files, and sets of related files, or packages of files, in a multi-host, multi-platform environment is provided. A public package client handles user requests to perform operations on a software package. Additionally, information about the package and the files contained therein may be obtained. A server, responsive to the client, performs the operations on the package. Data about the files is set in a data structure which may be stored in an archive along with the files themselves. In particular, this data may identify each file as either a text or binary file and as an executable file. A client may access the aforementioned data to determine if the file or files require further processing to adapt the file to the operating system on the client. Such processing may, for example, include linefeed/carriage return translation and codepage translation, or setting file attributes.

Abstract: A mechanism to acquire and deploy (“bootstrap”) software files, particularly testcase files, across multiple hosts and platforms is provided. A software package is created and a predetermined bootstrap executable file is built into the package. A process on each host on which the software files are to be deployed extracts the bootstrap file and executes it. Each bootstrap executable builds corresponding software files into the software package. The process then extracts the files corresponding to its particular process from the software package.

Abstract: Each client in an intranet includes at least the minimum functionality required to serve a remote request such as an HTTP request. Existing browsers within the intranet may share their collective local caches to form a scalable cache. The intranet proxy routes page requests from one client within the intranet to another when a local cache within the intranet contains a current copy of the requested page. A trust protocol insures that clients serving as caches may be trusted by the proxy, while a refresh mechanism such as a time-out policy ensures that the page is reloaded after a predetermined period of time. The collective cache thus scales with the number of browsers in the intranet, and existing browsers may be employed without direct modification. The same mechanism may be utilized, either within a network or through an Internet service provider, to permit individuals and companies to maintain Web sites on their own personal systems without paying fees for uninterrupted connection to the Internet.

Abstract: Digital signals defining a bit mapped primary image are stored in a data processing system and displayed on a color monitor. These signals are processed by breaking down or separating the primary image into a set of areas where the pixels within each area have the same color. The set of areas is then analyzed to select a group of a minimum number of subgroups, which group contains all of the different areas. Different color/dither patterns are assigned to represent the different subgroups. Then, a derivative bit mapped image is produced in which the assigned representations are used, and the derivative image is then printed or displayed.

Abstract: The door of a security enclosure has boltwork and a primary lock for locking the boltwork in its thrown condition. A drill-resistant disc is rotatably mounted between the lock and the exterior of the door, and the restraining wire of a relocker passes over the circumference of the disc. If a drilling attack is made on the lock the disc will be encountered and will be rotated by the drill tip to frustrate penetration of the disc by the drill. Furthermore, if the drill is aimed at the circumferential portion of the disc which guides the relocker wire any success in penetrating the disc will sever or dislodge the wire to allow the relocker to move under the action of a spring into a position in which it provides an additional locking action in the boltwork.