US6477665B1 — System, method, and article of manufacture for en…

Claim 1

Independent Claim 92 words

A method for implementing environment services patterns, comprising the steps of: (a) testing successfulness of an operation having pre-conditions and post-conditions that must be satisfied for an operation to be successful; (b) attempting to detect an orphaned server context; (c) creating a common interface for exception handling; (d) recording exception handling requirements for maintaining a consistent error handling approach; (e) distributing incoming requests amongst server components for optimizing usage of resources; and (f) minimizing the amount of changes that need to be made to exception handling logic when new exceptions are added.

Claim 2

Independent Claim 92 words

A method for implementing environment services patterns, comprising the steps of: (a) testing successfulness of an operation having pre-conditions and post-conditions that must be satisfied for an operation to be successful; (b) attempting to detect an orphaned server context; (c) creating a common interface for exception handling; (d) recording exception handling requirements for maintaining a consistent error handling approach; (e) distributing incoming requests amongst server components for optimizing usage of resources; and (f) minimizing the amount of changes that need to be made to exception handling logic when new exceptions are added.

Claim 3

Dependent Claim 72 words

A method as recited in claim 1 , wherein the step of testing successfulness of the operation includes the steps of: raising a first assertion asserting a pre-condition that must evaluate to true if the operation is successful; executing the operation; raising a second assertion asserting a post-condition that must evaluate to true if the operation is successful; and outputting an error message upon failure of at least one of the assertions.

Claim 4

Dependent Claim 141 words

A method as recited in claim 1 , wherein the step of attempting to detect the orphaned server context includes the steps of: maintaining a collection of outstanding server objects; creating a list of contexts for each of the outstanding server objects; adding to the list a compilation of clients who are interested in each of the outstanding server objects; recording on the list a duration of time since the clients invoked a method accessing each of the contexts of the outstanding server objects; examining the list at predetermined intervals for determining whether a predetermined amount of time has passed since each of the objects has been accessed; selecting contexts that have not been accessed in the predetermined amount of time; and sending information to the clients identifying the contexts that have not been accessed in the predetermined amount of time.

Claim 5

Dependent Claim 97 words

A method as recited in claim 1 , wherein the step of creating a common interface for exception handling includes the steps of: determining naming conventions of exceptions; adding at least one of a prefix and a suffix to each exception interface name for indicating that the exception interface is an exception; indicating where an exception error occurred; determining what caused the exception error; providing context as to what was happening when the exception error occurred; allowing streaming of the exception to a common interface; and outputting an error message indicating that an exception error has occurred.

Claim 6

Dependent Claim 85 words

A method as recited in claim 1 , wherein the step of distributing incoming requests amongst server components for optimizing usage of resources includes the steps of: receiving incoming requests; storing the requests; determining an availability of server components; compiling a listing of available server components; determining which server component on the listing of available server components is most appropriate to receive a particular request; and sending each particular request to the selected server component determined to be most appropriate to receive the particular request.

Claim 7

Dependent Claim 89 words

A method as recited in claim 1 , wherein the step of minimizing the amount of changes that need to be made to exception handling logic when new exceptions are added includes the steps of: organizing exceptions into hierarchies in a polymorphic exception handler; catching a root of one of the hierarchies in which an exception occurs; instructing the exception to rethrow itself; catching the rethrown exception; identifying the rethrown exception; determining a type of the rethrown exception; and outputting a message indicating the type of the rethrown exception.

Claim 8

Dependent Claim 120 words

A computer program embodied on a computer readable medium for implementing environment services patterns, comprising: (a) a code segment for testing successfulness of an operation having pre-conditions and post-conditions that must be satisfied for an operation to be successful; (b) a code segment for attempting to detect an orphaned server context; (c) a code segment for creating a common interface for exception handling; (d) a code segment for recording exception handling requirements for maintaining a consistent error handling approach; (e) a code segment for distributing incoming requests amongst server components for optimizing usage of resources; and (f) a code segment for minimizing the amount of changes that need to be made to exception handling logic when new exceptions are added.

Claim 9

Dependent Claim 120 words

A computer program embodied on a computer readable medium for implementing environment services patterns, comprising: (a) a code segment for testing successfulness of an operation having pre-conditions and post-conditions that must be satisfied for an operation to be successful; (b) a code segment for attempting to detect an orphaned server context; (c) a code segment for creating a common interface for exception handling; (d) a code segment for recording exception handling requirements for maintaining a consistent error handling approach; (e) a code segment for distributing incoming requests amongst server components for optimizing usage of resources; and (f) a code segment for minimizing the amount of changes that need to be made to exception handling logic when new exceptions are added.

Claim 10

Dependent Claim 71 words

A computer program as recited in claim 7 , wherein the code segment for testing successfulness of the operation includes: raising a first assertion asserting a pre-condition that must evaluate to true if the operation is successful; executing the operation; raising a second assertion asserting a post-condition that must evaluate to true if the operation is successful; and outputting an error message upon failure of at least one of the assertions.

Claim 11

Dependent Claim 140 words

A computer program as recited in claim 7 , wherein the code segment for attempting to detect the orphaned server context includes: maintaining a collection of outstanding server objects; creating a list of contexts for each of the outstanding server objects; adding to the list a compilation of clients who are interested in each of the outstanding server objects; recording on the list a duration of time since the clients invoked a method accessing each of the contexts of the outstanding server objects; examining the list at predetermined intervals for determining whether a predetermined amount of time has passed since each of the objects has been accessed; selecting contexts that have not been accessed in the predetermined amount of time; and sending information to the clients identifying the contexts that have not been accessed in the predetermined amount of time.

Claim 12

Dependent Claim 96 words

A computer program as recited in claim 7 , wherein the code segment for creating a common interface for exception handling includes: determining naming conventions of exceptions; adding at least one of a prefix and a suffix to each exception interface name for indicating that the exception interface is an exception; indicating where an exception error occurred; determining what caused the exception error; providing context as to what was happening when the exception error occurred; allowing streaming of the exception to a common interface; and outputting an error message indicating that an exception error has occurred.

Claim 13

Dependent Claim 84 words

A computer program as recited in claim 7 , wherein the code segment for distributing incoming requests amongst server components for optimizing usage of resources includes: receiving incoming requests; storing the requests; determining an availability of server components; compiling a listing of available server components; determining which server component on the listing of available server components is most appropriate to receive a particular request; and sending each particular request to the selected server component determined to be most appropriate to receive the particular request.

Claim 14

Dependent Claim 88 words

A computer program as recited in claim 7 , wherein the code segment for minimizing the amount of changes that need to be made to exception handling logic when new exceptions are added includes: organizing exceptions into hierarchies in a polymorphic exception handler; catching a root of one of the hierarchies in which an exception occurs; instructing the exception to rethrow itself; catching the rethrown exception; identifying the rethrown exception; determining a type of the rethrown exception; and outputting a message indicating the type of the rethrown exception.

Claim 15

Independent Claim 101 words

A system for implementing environment services patterns, comprising: (a) logic for testing successfulness of an operation having pre-conditions and post-conditions that must be satisfied for an operation to be successful; (b) logic for attempting to detect an orphaned server context; (c) logic for creating a common interface for exception handling; (d) logic for recording exception handling requirements for maintaining a consistent error handling approach; (e) logic for distributing incoming requests amongst server components for optimizing usage of resources; and (f) logic for minimizing the amount of changes that need to be made to exception handling logic when new exceptions are added.

Claim 16

Independent Claim 101 words

A system for implementing environment services patterns, comprising: (a) logic for testing successfulness of an operation having pre-conditions and post-conditions that must be satisfied for an operation to be successful; (b) logic for attempting to detect an orphaned server context; (c) logic for creating a common interface for exception handling; (d) logic for recording exception handling requirements for maintaining a consistent error handling approach; (e) logic for distributing incoming requests amongst server components for optimizing usage of resources; and (f) logic for minimizing the amount of changes that need to be made to exception handling logic when new exceptions are added.

Claim 17

Dependent Claim 69 words

A system as recited in claim 13 , wherein the logic for testing successfulness of the operation includes: raising a first assertion asserting a pre-condition that must evaluate to true if the operation is successful; executing the operation; raising a second assertion asserting a post-condition that must evaluate to true if the operation is successful; and outputting an error message upon failure of at least one of the assertions.

Claim 18

Dependent Claim 138 words

A system as recited in claim 13 , wherein the logic for attempting to detect the orphaned server context includes: maintaining a collection of outstanding server objects; creating a list of contexts for each of the outstanding server objects; adding to the list a compilation of clients who are interested in each of the outstanding server objects; recording on the list a duration of time since the clients invoked a method accessing each of the contexts of the outstanding server objects; examining the list at predetermined intervals for determining whether a predetermined amount of time has passed since each of the objects has been accessed; selecting contexts that have not been accessed in the predetermined amount of time; and sending information to the clients identifying the contexts that have not been accessed in the predetermined amount of time.

Claim 19

Dependent Claim 94 words

A system as recited in claim 13 , wherein the logic for creating a common interface for exception handling includes: determining naming conventions of exceptions; adding at least one of a prefix and a suffix to each exception interface name for indicating that the exception interface is an exception; indicating where an exception error occurred; determining what caused the exception error; providing context as to what was happening when the exception error occurred; allowing streaming of the exception to a common interface; and outputting an error message indicating that an exception error has occurred.

Claim 20

Dependent Claim 82 words

A system as recited in claim 13 , wherein the logic for distributing incoming requests amongst server components for optimizing usage of resources includes: receiving incoming requests; storing the requests; determining an availability of server components; compiling a listing of available server components; determining which server component on the listing of available server components is most appropriate to receive a particular request; and sending each particular request to the selected server component determined to be most appropriate to receive the particular request.

Claim 21

Dependent Claim 86 words

A system as recited in claim 13 , wherein the logic for minimizing the amount of changes that need to be made to exception handling logic when new exceptions are added includes: organizing exceptions into hierarchies in a polymorphic exception handler; catching a root of one of the hierarchies in which an exception occurs; instructing the exception to rethrow itself; catching the rethrown exception; identifying the rethrown exception; determining a type of the rethrown exception; and outputting a message indicating the type of the rethrown exception.

Annuity Stage	Window Opens	Payment Deadline	Surcharge Period Until	Estimated Fee	Status
3.5 Years (Year 4)	2005-11-04	2006-05-06	2006-11-05	$2000.00	Window Closed / Lapsed
7.5 Years (Year 8)	2009-11-04	2010-05-06	2010-11-05	$3760.00	Window Closed / Lapsed
11.5 Years (Year 12)	2013-11-04	2014-05-06	2014-11-05	$7700.00	Window Closed / Lapsed

System, method, and article of manufacture for environment services patterns in a netcentic environment

Abstract

Inventors

Bibliographic Details

Claims Analysis

References Cited (Backward Citations)

USPTO Annuity & Maintenance Windows

Assigned Categories & Tags

Assign Category Tag