Abstract: A master license entry that links a software application to a user identification can be made. Application licenses to use the software application can be roamed to multiple computing machines. Feature licenses for added features of the software application can be roamed to those computing machines as well. Multiple overlapping license rights for the software application may be linked to the master license entry. A count of how many license rights for the software application are linked to the master license entry can be maintained. Requests for licenses may be refused if the count of license rights has reached zero.

Abstract: A master license entry that links a software application to a user identification can be made. Application licenses to use the software application can be roamed to multiple computing machines. Feature licenses for added features of the software application can be roamed to those computing machines as well. Multiple overlapping license rights for the software application may be linked to the master license entry. A count of how many license rights for the software application are linked to the master license entry can be maintained. Requests for licenses may be refused if the count of license rights has reached zero.

Abstract: One or more techniques and/or systems are disclosed for generating a developer license that allows a developer application to run on developer machine. A user identification (userID) used to register a user can be used by the user to register as a developer. The userID can be authenticated for the registered developer. Further, a machine used by the developer for the developer application can be registered, and a resulting hardware identification (hardwareID) can be authenticated for the registered developer machine. Additionally, a developer certificate can be generated for the registered developer. The developer certificate can be authenticated and used to sign the developer application. The developer license can be generated for the developer, allowing the developer machine to execute the developer application, based at least upon the authenticated userID, the authenticated hardwareID, and the authenticated developer certificate.

Abstract: One or more techniques and/or systems are disclosed for generating a developer license that allows a developer application to run on developer machine. A user identification (userID) used to register a user can be used by the user to register as a developer. The userID can be authenticated for the registered developer. Further, a machine used by the developer for the developer application can be registered, and a resulting hardware identification (hardwareID) can be authenticated for the registered developer machine. Additionally, a developer certificate can be generated for the registered developer. The developer certificate can be authenticated and used to sign the developer application. The developer license can be generated for the developer, allowing the developer machine to execute the developer application, based at least upon the authenticated userID, the authenticated hardwareID, and the authenticated developer certificate.

Abstract: One or more techniques and/or systems are disclosed for generating a test application license for a developer application, such as to test a licensing portion of the developer application on a developer machine. An application identifier (appID) can be created that is particular to the developer application. Developer binding data associated with an authenticated developer of the developer application can be created that is particular to the developer. The appID and developer binding data are combined to create bound application developer data. The test application license is generated for the developer application based at least upon an authenticated developer certificate and the bound application developer data. The generated test application license provides for the licensing portion of the developer application to be tested on the developer machine.

Abstract: The claimed subject matter provides a method for licensing software in a computing environment. An exemplary method includes initiating application software program on a computer system having a plurality of authorized users, one of the authorized users having a single-user license to use the software program. An identity of a current user of the computer system is checked. Operation of the software program is prohibited if the current user is one of the plurality of authorized users other than the user who is granted the single-user license.

Abstract: The claimed subject matter provides a method for revoking licensed software in a computing environment. An exemplary method includes receiving a machine ID from a computer system. An application program and a license credential for the application program are sent to the computer system. Subsequently, upon theft or other loss of the computer system, a request to revoke the license credential is received. The request identifies the machine ID. When the computer system subsequently initiates a connection, the connection is detected based on the machine ID. An indication that the license credential for the application program is revoked is sent to the computer system. When the application program is later initiated, its operation is disabled because of the revocation of the license credential.

Abstract: The claimed subject matter provides a method for managing license upgrades in a computing environment. An exemplary method includes sending a request to upgrade a license status of application software program. The method further includes receiving licensing information indicating a change to the license status of the software program, the change to the license status of the software program being sufficient to allow the user to use the software program under the changed status automatically, and without further action by a user.

Abstract: A master license entry that links a software application to a user identification can be made. Application licenses to use the software application can be roamed to multiple computing machines. Feature licenses for added features of the software application can be roamed to those computing machines as well. Multiple overlapping license rights for the software application may be linked to the master license entry. A count of how many license rights for the software application are linked to the master license entry can be maintained. Requests for licenses may be refused if the count of license rights has reached zero.

Abstract: An input URL string is searched for a particular pattern, the pattern being defined in a manner such that the search may be satisfied while allowing variability among constituent parts of the input URL string. The input URL string is mapped to an output URL string if the pattern is found in the input URL string.

Abstract: Methods and systems for rendering information pages are described. A page is divided into panes which are rendered by individual pane renderers. The pane renderers can be shared between pages, or even re-used across multiple applications. Rendering support components or objects are provided and can provide access to shared services or data (e.g. ads, user preferences, scripts, and styles) that might be required by multiple panes on a page. Page descriptions comprising pane renderers are created dynamically in a prescribed fashion by an application. A page renderer service in a platform then processes the page description and causes the appropriate RSOs to be called, initialized, and used by the pane renderers to render the page.

Abstract: An input URL string is searched for a particular pattern, the pattern being defined in a manner such that the search may be satisfied while allowing variability among constituent parts of the input URL string. The input URL string is mapped to an output URL string if the pattern is found in the input URL string.

Abstract: The invention provides for flexible, convenient, and dynamic URL mapping methods and systems by providing generalized approaches which specify patterns in term of recognizable syntax. The recognizable syntax can be defined by one or more rules. The rules are used and applied to an input URL string which is provided by a client to map the input URL string to an output URL string which is used by a rendering engine to provide a requested resource. Embodiments of the invention provide for a rule cache or internal store in which rules are kept. The rule cache allows for rules to be added, deleted, or modified as desired, without the need to stop and re-start the web service. The rule cache can be populated dynamically at run time. In addition, embodiments of the invention conveniently group rules into rule groups. Individual rule groups can be selectively applied to an input URL string.