Abstract: Under the present invention, when a TCS receives a data command (e.g., a read or write command) pursuant to a communication session between the TCS and an application, it will first request permission from a permission system to execute the data command. By applying a set of rules to a setting of a state variable associated with the TCS, the permission system will determine whether to grant the permission. If so, the TCS will execute the data command and change the setting of the state variable. If a close command is later received by the TCS to close the communication session, permission will once again be requested from the permission system, which will again apply a set of rules to the current setting of the state variable to determine if the session can be safely closed.

Abstract: A method for filtering data packets through computers on the Internet that allows a computer to determine whether an incoming numbered list is present in a numbered list data set faster than the prior art methods. The present invention comprises an Array Creation Program (ACP) and an Array Matching Program (AMP). The ACP creates a plurality of arrays from the numbered list data set. The values of the array fields are based on the numbers in the numbered lists. The AMP analyzes the numbers in the incoming numbered list to determine the hexadecimal values in the array fields associated with the numbers in the incoming numbered list. The AMP uses a counter to process the numbers in the incoming numbered list. If the counter becomes zero, then the incoming numbered list is not present in the numbered list data set. An embodiment utilizing hashtables is also disclosed.

Abstract: The present invention is a method, system and apparatus for memory leak detection and reporting. In a preferred method of the invention, allocated ones of resources in a resource pool can be time stamped upon allocation and calling code segments receiving the allocated resources can be identified. Memory leaks can be detected by inspecting individual timestamps for the allocated resources to determine whether the allocated resources have become overly idle. Notably, the identifying step can include the step of retrieving identities for individual ones of the calling code segments from an associated calling stack when the individual ones of the calling code segments acquire one of the allocated resources. In any case, for each allocated resource determined to have become overly idle, an identity of a corresponding one of the calling code segments can be reported.