Virtual machine

摘要

The present invention is directed to various systems and/or methods relating to a software platform that provides for authentication of a requestor. Preferably, this authentication happens before there is an opportunity for any resource intensive request to harm operation of the system. Preferably, a reliability level is based on authentication so that the amount and/or type of resource access is controlled based, at least in part, on the authentication information. Preferably, heap usage is controlled by this reliability level. Preferably, the software platform is a virtual machine, preferably the Java Virtual Machine.

主权项

1. A method of using a software platform, wherein the software platform is a virtual machine (VM) including a heap memory, the method comprising the steps of:
receiving a request from a requestor; determining authentication information in the received request; adding the requestor to a blacklist if certain predetermined conditions exist, wherein said predetermined conditions exist when the requester has made at least one resource intensive request, wherein said at least one resource intensive request comprises at least one resource intensive XML document; setting a reliability level from among a plurality of reliability levels based on the authentication information determined in the determining step, wherein the plurality of reliability levels includes a blacklisted level, and wherein said reliability level is set at said blacklisted level if the requester is added to the blacklist at the adding step; allocating, by a servlet container, a pooled servlet thread in response to the request; and setting, after the setting step, a resource allocation allowed in a response to the request as controlled by the software platform if the reliability level set at the setting step is not the blacklisted level, wherein the resource allocation includes an upper limit on heap usage for said thread based on the reliability level set at the setting step, and further wherein the controlling step is performed before the request becomes a resource intensive request; providing the ability to change the previously set upper limit on heap usage and request processing priority using credit information based on the authentication information before processing the request made by the requestor; and rejecting a resource allocation allowed in a response to the request as controlled by the software platform if the reliability level set at the setting step is the blacklisted level.