Abstract: Handle configurations are disclosed for powered implements having a shaft, allowing the implements to be holdable by both hands of a user. An exemplary implement has an elongated shaft having first and second end portions. A first handhold is adjustably mounted to the shaft and extends outwardly therefrom. A second handhold is adjustably mounted either to the shaft or to an elongated member coupled to the shaft. The elongated member can include a mounting portion and a handle portion providing the second handhold. The mounting portion mounts to the first end portion at a mounting location. The first and second handholds allow operation of the implement by a user with arms in respective neutral arm positions and hands in respective neutral gripping positions. The elongated member allows transmission of a force applied to the second handhold by the user through the elongated member and to the elongated shaft at the mounting location.

Abstract: Handle configurations are disclosed for powered implements having a shaft, allowing the implements to be holdable by both hands of a user. An exemplary implement has an elongated shaft having first and second end portions. A first handhold is adjustably mounted to the shaft and extends outwardly therefrom. A second handhold is adjustably mounted either to the shaft or to an elongated member coupled to the shaft. The elongated member can include a mounting portion and a handle portion providing the second handhold. The mounting portion mounts to the first end portion at a mounting location. The first and second handholds allow operation of the implement by a user with arms in respective neutral arm positions and hands in respective neutral gripping positions. The elongated member allows transmission of a force applied to the second handhold by the user through the elongated member and to the elongated shaft at the mounting location.

Abstract: Technology for monitoring transactions in a computing environment is disclosed. Execution of a transaction by a first application is monitored by a first software entity executing on a first computing device. Performance data that relates to execution of the transaction by a first application is generated. Execution of the transaction by a second application is monitored by a second software entity. The transaction is executed by the second application based on a request from the first application. A determination is made, based on the monitoring, that the first software entity should report the performance data to a third software entity that executes on a second computing device. Based on determining that the first software entity should report the performance data, data is propagated that indicates that the first software entity should report the performance data. The first software entity reports the performance data to the third software entity.

Abstract: Relationships between components in an application and the services they provide are identified, including redundant caller-callee sequences. Specific components of interest are instrumented to obtain data when they execute. Data structures are created which identify the components and their dependencies on one other. To avoid excessive overhead costs, redundant dependencies are identified. A dependency data structure can be provided for each unique dependency. When repeated instances of a dependency are detected, the associated dependency data structure can be augmented with correlation data of the repeated instances, such as transaction identifiers and sequence identifiers. Sequence identifiers identify an order in which a component is called. A flag can be used to force the creation of a new dependency data structure, and a calling component's name can be used instead of a sequence identifier. Agents report the dependency data structures to a manager to provide graph data in a user interface.

Abstract: Monitoring asynchronous transactions in a computing environment is disclosed. A first unique identifier is determined when a first method executes. The identifier is associated with an asynchronous transaction. A second unique identifier is determined when a second method executes. If it is determined that the first unique identifier and the second unique identifier match, then is it determined that the asynchronous transaction started with the first method and completed with the second method. In one embodiment, code that identifies a routine that has instructions for determining the first unique identifier at runtime is added to the first method, and code that identifies a routine that has instructions for determining the second unique identifier at runtime is added to the second method.

Abstract: Technology for monitoring transactions in a computing environment is disclosed. Execution of a transaction by a first application is monitored by a first software entity executing on a first computing device. Performance data that relates to execution of the transaction by a first application is generated. Execution of the transaction by a second application is monitored by a second software entity. The transaction is executed by the second application based on a request from the first application. A determination is made, based on the monitoring, that the first software entity should report the performance data to a third software entity that executes on a second computing device. Based on determining that the first software entity should report the performance data, data is propagated that indicates that the first software entity should report the performance data. The first software entity reports the performance data to the third software entity.

Abstract: Relationships between components in an application and the services they provide are identified, including redundant caller-callee sequences. Specific components of interest are instrumented to obtain data when they execute. Data structures are created which identify the components and their dependencies on one other. To avoid excessive overhead costs, redundant dependencies are identified. A dependency data structure can be provided for each unique dependency. When repeated instances of a dependency are detected, the associated dependency data structure can be augmented with correlation data of the repeated instances, such as transaction identifiers and sequence identifiers. Sequence identifiers identify an order in which a component is called. A flag can be used to force the creation of a new dependency data structure, and a calling component's name can be used instead of a sequence identifier. Agents report the dependency data structures to a manager to provide graph data in a user interface.

Abstract: Monitoring asynchronous transactions in a computing environment is disclosed. A first unique identifier is determined when a first method executes. The identifier is associated with an asynchronous transaction. A second unique identifier is determined when a second method executes. If it is determined that the first unique identifier and the second unique identifier match, then is it determined that the asynchronous transaction started with the first method and completed with the second method. In one embodiment, code that identifies a routine that has instructions for determining the first unique identifier at runtime is added to the first method, and code that identifies a routine that has instructions for determining the second unique identifier at runtime is added to the second method.

Abstract: In accordance with the present invention a method and system for transmitting multibyte characters in a network comprises the steps, performed by a processor, of receiving a set of fixed-length characters; converting each fixed-length character into a multibyte character to determine a length corresponding to the multibyte characters; and transmitting the length and the multibyte characters.

Abstract: In accordance with the present invention a method and system for transmitting multibyte characters in a network comprises the steps, performed by a processor, of receiving a set of fixed-length characters; converting each fixed-length character into a multibyte character to determine a length corresponding to the multibyte characters; and transmitting the length and the multibyte characters.

Abstract: In accordance with the present invention a method and system for transmitting multibyte characters in a network comprises the steps, performed by a processor, of receiving a set of fixed-length characters; converting each fixed-length character into a multibyte character to determine a length corresponding to the multibyte characters; and transmitting the length and the multibyte characters.

Abstract: In accordance with the present invention a method and system for transmitting multibyte characters in a network comprises the steps, performed by a processor, of receiving a set of fixed-length characters; converting each fixed-length character into a multibyte character to determine a length corresponding to the multibyte characters; and transmitting the length and the multibyte characters.