Abstract: Systems and methods for allocating computing resources for a multi-tiered application are disclosed. A computer-implemented method includes: determining, by a computing device, a topology of a multi-tiered application; determining, by the computing device, a modeled setting of a computing resource for the multi-tiered application based on the determined topology; determining, by the computing device, an actual usage of the computing resource by the multi-tiered application; and adjusting, by the computing device, an allocation of the computing resource to the multi-tiered application based on the actual usage and the modeled setting.

Abstract: Systems and methods for allocating computing resources for a multi-tiered application are disclosed. A computer-implemented method includes: determining, by a computing device, a topology of a multi-tiered application; determining, by the computing device, a modeled setting of a computing resource for the multi-tiered application based on the determined topology; determining, by the computing device, an actual usage of the computing resource by the multi-tiered application; and adjusting, by the computing device, an allocation of the computing resource to the multi-tiered application based on the actual usage and the modeled setting.

Abstract: Systems and methods for allocating computing resources for a multi-tiered application are disclosed. A computer-implemented method includes: determining, by a computing device, a topology of a multi-tiered application; determining, by the computing device, a modeled setting of a computing resource for the multi-tiered application based on the determined topology; determining, by the computing device, an actual usage of the computing resource by the multi-tiered application; and adjusting, by the computing device, an allocation of the computing resource to the multi-tiered application based on the actual usage and the modeled setting.

Abstract: Systems and methods for allocating computing resources for a multi-tiered application are disclosed. A computer-implemented method includes: determining, by a computing device, a topology of a multi-tiered application; determining, by the computing device, a modeled setting of a computing resource for the multi-tiered application based on the determined topology; determining, by the computing device, an actual usage of the computing resource by the multi-tiered application; and adjusting, by the computing device, an allocation of the computing resource to the multi-tiered application based on the actual usage and the modeled setting.

Abstract: This document relates to medical devices (e.g., organ ports such as transapical heart ports) and methods and materials for implanting and using such medical devices. For example, organ ports and entry devices that can be used to implant an organ port are provided.

Abstract: A system for implanting a heart valve prosthesis in a patient's heart includes a balloon expandable, tissue, stented heart valve, and an apical valve delivery device for delivering the stented heart valve to a target site in the patient's heart. The delivery device includes an inflation balloon module for expanding the stented heart valve prosthesis, markers on the delivery device to assist in location of the delivery device at an appropriate location, and a streamlined cap.

Abstract: A system for implanting a heart valve prosthesis in a patient's heart includes a balloon expandable, tissue, stented heart valve and a transfemoral valve delivery device for delivering the stented heart valve to a target site in the patient's heart. The delivery device includes an inflation balloon module for expanding the stented heart valve prosthesis, markers on to assist in location of the delivery device at an appropriate location; and a streamlined cap.

Abstract: A hijack avoidance technique avoids presenting an access to more than one of a chain of authentication objects, such as a chain of Lightweight Directory Access Protocol (LDAP) authenticators. A pre-filter determines whether an authentication object should be presented with the access by comparing either all or a portion of a domain suffix, an IP address, or other identification other than the user ID with predetermined values. If the filter criterion is met, the associated authentication object accepts or rejects the access. Otherwise, the access is passed to the next authentication object in the chain. The first authentication object may be associated with a hosting entity and successive authentication objects each associated with different customers of the hosting entity.

Abstract: This document relates to medical devices (e.g., organ ports such as transapical heart ports) and methods and materials for implanting and using such medical devices. For example, organ ports and entry devices that can be used to implant an organ port are provided.

Abstract: This document relates to medical devices. For example, transapical heart ports, methods for making transapical heart ports, and methods for using transapical heart ports are provided.

Abstract: A hijack avoidance technique avoids presenting an access to more than one of a chain of authentication objects, such as a chain of Lightweight Directory Access Protocol (LDAP) authenticators. A pre-filter determines whether an authentication object should be presented with the access by comparing either all or a portion of a domain suffix, an IP address, or other identification other than the user ID with predetermined values. If the filter criterion is met, the associated authentication object accepts or rejects the access. Otherwise, the access is passed to the next authentication object in the chain. The first authentication object may be associated with a hosting entity and successive authentication objects each associated with different customers of the hosting entity.

Abstract: A system for implanting a heart valve prosthesis in a patient's heart includes a balloon expandable, tissue, stented heart valve, and an apical valve delivery device for delivering the stented heart valve to a target site in the patient's heart. The delivery device includes an inflation balloon module for expanding the stented heart valve prosthesis, markers on the delivery device to assist in location of the delivery device at an appropriate location, and a streamlined cap.

Abstract: A system for implanting a heart valve prosthesis in a patient's heart includes a balloon expandable, tissue, stented heart valve and a transfemoral valve delivery device for delivering the stented heart valve to a target site in the patient's heart. The delivery device includes an inflation balloon module for expanding the stented heart valve prosthesis, markers on to assist in location of the delivery device at an appropriate location; and a streamlined cap.

Abstract: A device for implanting an expandable heart valve prosthesis at a valve annulus in a patient's heart includes an implantation device configured to extend from a first opening in the patient's body, through the patient's aorta, through a valve annulus, through an opening in a ventricle, and to exit through the patient's thoracic region. The device further includes a port having a hemostasis valve for providing access through the patient's thoracic region and into the ventricle and at least two interchangeable modules configured for delivery using the implantation device.

Abstract: A method for implementing a front-end user sort request includes receiving a list request, decomposing the list request and creating a sort entry object using a list of column values initially retrieved from a data storage medium. A sort routine is performed on at least a first column of the list of column values in the sort entry object, wherein a compare function of the sort routine is dependent upon information obtained from decomposing the list request. The list request is rebuilt in accordance with the completion of the sort routine.

Abstract: A method for implementing a web-based, front-end user request includes receiving a list request from a front-end user, and receiving user characteristics associated with the list request. Data corresponding to the list request is retrieved from a data storage medium, and the retrieved data is configured in accordance with the user characteristics. The configured data is returned to the front-end user in accordance with the user characteristics.

Abstract: A method for implementing a front-end user sort request includes receiving a list request, decomposing the list request and creating a sort entry object using a list of column values initially retrieved from a data storage medium. A sort routine is performed on at least a first column of the list of column values in the sort entry object, wherein a compare function of the sort routine is dependent upon information obtained from decomposing the list request. The list request is rebuilt in accordance with the completion of the sort routine.

Abstract: A method for implementing a web-based, front-end user request includes receiving a list request from a front-end user, and receiving user characteristics associated with the list request. Data corresponding to the list request is retrieved from a data storage medium, and the retrieved data is configured in accordance with the user characteristics. The configured data is returned to the front-end user in accordance with the user characteristics.

Abstract: A method for implementing a front-end user sort request includes receiving a list request, decomposing the list request and creating a sort entry object using a list of column values initially retrieved from a data storage medium. A sort routine is performed on at least a first column of the list of column values in the sort entry object, wherein a compare function of the sort routine is dependent upon information obtained from decomposing the list request. The list request is rebuilt in accordance with the completion of the sort routine.

Abstract: A method for implementing a web-based, front-end user request includes receiving a list request from a front-end user, and receiving user characteristics associated with the list request. Data corresponding to the list request is retrieved from a data storage medium, and the retrieved data is configured in accordance with the user characteristics. The configured data is returned to the front-end user in accordance with the user characteristics.