US6334114B1 — Method and apparatus for performing transactions …

Claim 1

Independent Claim 188 words

A method for processing multiple-request transactions in a stateless environment, wherein the multiple-request transactions involve operations specified in browser messages, the method comprising the steps of: a cartridge execution engine intercepting browser messages directed to a cartridge; said cartridge execution engine determining whether said browser messages are associated with transactions; if said browser messages are associated with transactions, then said cartridge execution engine sending transaction control messages that are based on said browser messages to a transaction manager that is implemented separately from said cartridge; said cartridge execution engine sending operation messages that are based on said browser messages to said cartridge in response to said operation messages from said cartridge execution engine, said cartridge performing the operations specified in said operation messages without the cartridge persistently maintaining state information for the multiple-request transactions to which the operations belong; and in response to said transaction control messages from said cartridge execution engine, said transaction manager causing the operations specified in said operation messages that are performed by said cartridge as part of the multiple-request transactions to be either conmitted or rolled back as an atomic unit of work.

Claim 2

Independent Claim 188 words

A method for processing multiple-request transactions in a stateless environment, wherein the multiple-request transactions involve operations specified in browser messages, the method comprising the steps of: a cartridge execution engine intercepting browser messages directed to a cartridge; said cartridge execution engine determining whether said browser messages are associated with transactions; if said browser messages are associated with transactions, then said cartridge execution engine sending transaction control messages that are based on said browser messages to a transaction manager that is implemented separately from said cartridge; said cartridge execution engine sending operation messages that are based on said browser messages to said cartridge in response to said operation messages from said cartridge execution engine, said cartridge performing the operations specified in said operation messages without the cartridge persistently maintaining state information for the multiple-request transactions to which the operations belong; and in response to said transaction control messages from said cartridge execution engine, said transaction manager causing the operations specified in said operation messages that are performed by said cartridge as part of the multiple-request transactions to be either conmitted or rolled back as an atomic unit of work.

Claim 3

Dependent Claim 62 words

The method of claim 1 , wherein the step of causing the operations specified in said operation messages to be committed includes the step of said transaction manager sending commit messages to one or more database servers, wherein the commit messages cause said one or more database servers to commit changes associated with said multiple-reauest transactions as an atomic unit of work.

Claim 4

Dependent Claim 64 words

The method of claim 1 , wherein the step of causing the operations specified in said operation messages to be rolled back includes the step of said transaction manager sending rollback messages to one or more database servers, wherein the rollback messages cause said one or more database servers to roll back changes associated with said multiple-recst transactions as an atomic unit of work.

Claim 5

Dependent Claim 31 words

The method of claim 1 , wherein the browser messages associated with transactions are associated with transaction IDs, wherein the transaction IDs identify a browser associated with a particular browser message.

Claim 6

Dependent Claim 30 words

The method of claim 4 , wherein the transaction IDs are maintained as cookies, wherein the cookies are maintained on the browser that is associated with the particular browser message.

Claim 7

Dependent Claim 42 words

The method of claim 4 , wherein the transaction IDs are maintained as URLs that are associated with one or more tags in one or more Web pages that are displayed at the browser that is associated with the particular browser message.

Claim 8

Dependent Claim 63 words

The method of claim 1 , wherein the step of said cartridge execution engine determining whether said browser messages are associated with transactions includes the steps of: obtaining a URL that is associated with a particular browser message; and using the URL associated with the particular browser message to determine the state of a transaction that is associatd with the particular browser message.

Claim 9

Dependent Claim 36 words

The method of claim 4 , wherein the transaction IDs are associated with a timeout period, wherein the expiration of the timeout period indicates that the transaction associated with the transaction ID should be deemed invalid.

Claim 10

Dependent Claim 42 words

The method of claim 1 , wherein: prior to intercepting browser messages directed to the cartridge, registering the cartridge, wherein the cartridge is registered by storing metadata that defines a set of attributes that is associated with one or more transaction types.

Claim 11

Dependent Claim 50 words

The method of claim 1 , wherein the step of said cartridge execution engine determining whether said browser messages are associated with transactions includes the steps of: retrieving metadata based on the intercepted browser messages; and using the retrieved metadata to determine whether the browser messages are associated with transactions.

Claim 12

Dependent Claim 199 words

A computer readable medium carrying sequences of instructions for processing multiple-request transactions in a stateless environment, wherein the multiple-request transactions involve operations specified in browser messages, the sequences of instructions including instructions for performing the steps of: a cartridge execution engine intercepting browser messages directed to a cartridge; said cartridge execution engine determining whether said browser messages are associated with transactions; if said browser messages are associated with transactions, then said cartridge execution engine sending transaction control messages that are based on said browser messages to a transaction manager that is implemented separately from said cartride; said cartridge execution engine sending operation messages that are based on said browser messages to said cartridge in response to said operation messages from said cartridge execution engine, said cartridge performing the operations specified in said operation messages without the cartridge persistently maintaining state information for the multiple-request transactions to which the operations belong; and in response to said transaction control messages from said cartridge execution engine, said transaction manager causing the operations specified in said operation messages that are performed by said cartridge as part of the multiple-request transactions to be either committed or rolled back as an atomic unit of work.

Claim 13

Dependent Claim 199 words

A computer readable medium carrying sequences of instructions for processing multiple-request transactions in a stateless environment, wherein the multiple-request transactions involve operations specified in browser messages, the sequences of instructions including instructions for performing the steps of: a cartridge execution engine intercepting browser messages directed to a cartridge; said cartridge execution engine determining whether said browser messages are associated with transactions; if said browser messages are associated with transactions, then said cartridge execution engine sending transaction control messages that are based on said browser messages to a transaction manager that is implemented separately from said cartride; said cartridge execution engine sending operation messages that are based on said browser messages to said cartridge in response to said operation messages from said cartridge execution engine, said cartridge performing the operations specified in said operation messages without the cartridge persistently maintaining state information for the multiple-request transactions to which the operations belong; and in response to said transaction control messages from said cartridge execution engine, said transaction manager causing the operations specified in said operation messages that are performed by said cartridge as part of the multiple-request transactions to be either committed or rolled back as an atomic unit of work.

Claim 14

Dependent Claim 33 words

The computer readable medium of claim 11 , wherein the browser messages associated with transactions are associated with transaction IDs, wherein the transaction IDs identify a browser associated with a particular browser message.

Claim 15

Dependent Claim 65 words

The computer readable medium of claim 11 , wherein the step of said cartridge execution engine determining whether said browser messages are associated with transactions includes the steps of: obtaining a URL that is associated with a particular browser message; and using the URL associated with the particular browser message to determine the state of a transaction that is associate with the particular browser message.

Claim 16

Independent Claim 233 words

A system for processing multiple-request transactions in a stateless environment, wherein the mnultiple-request transactions involve operations specified in browser messages, the system comprising: a memory; one or more processors coupled to the memory; and a set of computer instructions contained in the memory, the set of computer instructions including computer instructions which when executed by the one or more processors, cause the one or more processors to perform the steps of: a cartridge execution engine intercepting browser messages directed to a cartridge; said cartridge execution engine determining whether said browser messages are associated with transactions; if said browser messages are associated with transactions, then said cartridge execution engine sending transaction control messages that are based on said browser messages to a transaction manager that is implemented separately from said cartridge; said cartridge execution engine sending operation messages that are based on said browser messaes to said cartridge; in response to said operation mnessaes from said cartridge execution engine, said cartridge perfoming the operations specified in said operation messages without the cartridge persistently maintaining state information for the multiple-request transactions to which the operations belong; and in response to said transaction control messages from said cartridge execution engine, said transaction manager causing the operations specified in said operation messages that are performed by said cartridge as part of the multiple-request transactions to be either committed or rolled back as an atomic unit of work.

Claim 17

Independent Claim 233 words

A system for processing multiple-request transactions in a stateless environment, wherein the mnultiple-request transactions involve operations specified in browser messages, the system comprising: a memory; one or more processors coupled to the memory; and a set of computer instructions contained in the memory, the set of computer instructions including computer instructions which when executed by the one or more processors, cause the one or more processors to perform the steps of: a cartridge execution engine intercepting browser messages directed to a cartridge; said cartridge execution engine determining whether said browser messages are associated with transactions; if said browser messages are associated with transactions, then said cartridge execution engine sending transaction control messages that are based on said browser messages to a transaction manager that is implemented separately from said cartridge; said cartridge execution engine sending operation messages that are based on said browser messaes to said cartridge; in response to said operation mnessaes from said cartridge execution engine, said cartridge perfoming the operations specified in said operation messages without the cartridge persistently maintaining state information for the multiple-request transactions to which the operations belong; and in response to said transaction control messages from said cartridge execution engine, said transaction manager causing the operations specified in said operation messages that are performed by said cartridge as part of the multiple-request transactions to be either committed or rolled back as an atomic unit of work.

Claim 18

Dependent Claim 31 words

The system of claim 14 , wherein the browser messages associated with transactions are associated with transaction IDs, wherein the transaction IDs identify a browser associated with a particular browser message.

Claim 19

Dependent Claim 63 words

The system of claim 14 , wherein the step of said cartridge execution engine determining whether said browser messages are associated with transactions includes the steps of: obtaining a URL that is associated with a particular browser message; and using the URL associated with the particular browser message to determine the state of a transaction that is associate with the particular browser message.

Claim 20

Dependent Claim 74 words

The method of claim 1 , wherein: the step of said cartridge execution engine intercepting browser messages includes the step of said cartridge execution engine intercepting browser messages that include a begin transaction command; and in response to said cartridge execution engine receiving a browser message that includes a begin transaction command, said cartridge execution engine sending a transaction control message to said transaction manager to cause said transaction manager to begin said transaction.

Claim 21

Dependent Claim 74 words

The method of claim 1 , wherein: the step of said cartridge execution engine intercepting browser messages includes the step of said cartridge execution engine intercepting browser messages that include a commit transaction command; and in response to said cartridge execution engine receiving a browser message that includes a commit transaction command, said cartridge execution engine sending a transaction control message to said transaction manager to cause said transaction manager to commit said transaction.

Claim 22

Dependent Claim 75 words

The method of claim 1 , wherein: the step of said cartridge execution engine intercepting browser messages includes the step of said cartridge execution engine intercepting browser messages that include a rollback transaction command; and in response to said cartridge execution engine receiving a browser message that includes a rollback transaction command, said cartridge execution engine sending a transaction control message to said transaction manager to cause said transaction manager to roll back said transaction.

Claim 23

Dependent Claim 46 words

The method of claim 17 , further comprising the step of receiving said begin transaction command in the form of a URL at said cartridge execution engine in response to selection of a control associated with a tag of a Web page displayed at the browser.

Claim 24

Dependent Claim 46 words

The method of claim 18 , firther comprising the step of receiving said commit transaction command in the form of a URL at said cartridge execution engine in response to selection of a control associated with a tag of a Web page displayed at the browser.

Claim 25

Dependent Claim 46 words

The method of claim 19 , further comprising the step of receiving said rollback transaction command in the form of a URL at said cartridge execution engine in response to selection of a control associated with a tag of a Web page displayed at the browser.

Claim 26

Dependent Claim 64 words

The computer readable medium of claim 11 , wherein the step of causing the operations specified in said operation messages to be committed includes the step of said transaction manager sending commit messages to one or more database servers, wherein the commit messages cause said one or more database servers to commit changes associated with said multiple-request transactions as an atomic unit of work.

Claim 27

Dependent Claim 66 words

The computer readable medium of claim 11 , wherein the step of causing the operations specified in said opcration messages to be rolled back includes the step of said transaction manager sending rollback messages to one or more database servers, wherein the rollback messages cause said one or more database servers to roll back changes associated with said multiple-request transactions as an atomic unit of work.

Claim 28

Dependent Claim 88 words

The computer readable medium of claim 11 , wherein the step of said cartridge execution engine intercepting browser messages includes the step of said cartridge execution engine intercepting browser messages that include a begin transaction command; and the computer readable medium further comprising instructions for performing the step of, in response to said cartridge execution engine receiving a browser message that includes a begin transaction command, said cartridge execution engine sending a transaction control message to said transaction manager to cause said transaction manager to begin said transaction.

Claim 29

Dependent Claim 88 words

The computer readable medium of claim 11 , wherein the step of said cartridge execution engine intercepting browser messages includes the step of said cartridge execution engine intercepting browser messages that include a commit transaction command; and the computer readable medium further comprising instructions for performing the step of, in response to said cartridge execution engine receiving a browser message that includes a commit transaction command, said cartridge execution engine sending a transaction control message to said transaction manager to cause said transaction manager to commit said transaction.

Claim 30

Dependent Claim 89 words

The computer readable medium of claim 11 , wherein the step of said cartridge execution engine intercepting browser messages includes the step of said cartridge execution engine intercepting browser messages that include a rollback transaction command; and the computer readable medium further comprising instructions for performing the step of, in response to said cartridge execution engine receiving a browser message that includes a rollback transaction command, said cartridge execution engine sending a transaction control message to said transaction manager to cause said transaction manager to roll back said transaction.

Claim 31

Dependent Claim 34 words

The computer readable medium of claim 12 , further comprising instructions for maintaining the transaction IDs as cookies, wherein the cookies are maintained on the browser that is associated with the particular browser message.

Claim 32

Dependent Claim 48 words

The computer readable medium of claim 12 , further comprising instructions for maintaining the transaction IDs as URLs, wherein the URLs are associated with one or more tags in one or more Web pages that are displayed at the browser that is associated with the particular browser message.

Claim 33

Dependent Claim 40 words

The computer readable medium of claim 12 , further comprising instructions for associating a timeout period with the transaction IDs, wherein the expiration of the timeout period indicates that the transaction associated with the transaction ID should be deemed invalid.

Claim 34

Dependent Claim 51 words

The computer readable medium of claim 11 , further comprising instructions for performing the steps of prior to intercepting browser messages directed to the cartridge, registering the cartridge, wherein the cartridge is registered by storing metadata that defines a set of attributes that is associated with one or more transaction types.

Claim 35

Dependent Claim 52 words

The computer readable medium of claim 11 , wherein the step of said cartridge execution engine determining whether said browser messages are associated with transactions includes the steps of: retrieving metadata based on the intercepted browser messages; and using the retrieved metadata to determine whether the browser messages are associated with transactions.

Claim 36

Dependent Claim 51 words

The computer readable medium of claim 25 , further comprising instructions for performing the step of receiving said begin transaction command in the form of a URL at said cartridge execution engine in response to selection of a control associated with a tag of a Web page displayed at the browser.

Claim 37

Dependent Claim 51 words

The computer readable medium of claim 26 , further comprising instructions for performing the step of receiving said commit transaction command in the form of a URL at said cartridge execution engine in response to selection of a control associated with a tag of a Web page displayed at the browser.

Claim 38

Dependent Claim 51 words

The computer readable medium of claim 27 , further comprising instructions for performing the step of receiving said rollback transaction command in the form of a URL at said cartridge execution engine in response to selection of a control associated with a tag of a Web page displayed at the browser.

Claim 39

Dependent Claim 62 words

The system of claim 14 , wherein the step of causing the operations specified in said operation messages to be committed includes the step of said transaction manager sending commit messages to one or more database servers, wherein the commit messages cause said one or more database servers to commit changes associated with said multiple-request transactions as an atomic unit of work.

Claim 40

Dependent Claim 63 words

The system of claim 14 , wherein the step of causing operations specified in said operation messages to be rolled back includes the step of said transaction manager sending rollback messages to one or more database servers, wherein the rollback messages cause said one or more database servers to roll back changes associated with said multiple-request transactions as an atomic unit of work.

Claim 41

Dependent Claim 74 words

The system of claim 14 , wherein the step of said cartridge execution engine intercepting browser messages includes the step of said cartridge execution engine intercepting browser messages that include a begin transaction command; and in response to said cartridge execution engine receiving a browser message that includes a begin transaction command, said cartridge execution engine sending a transaction control message to said transaction manager to cause said transaction manager to begin said transaction.

Claim 42

Dependent Claim 74 words

The system of claim 14 , wherein the step of said cartridge execution engine intercepting browser messages includes the step of said cartridge execution engine intercepting browser messages that include a commit transaction command; and in response to said cartridge execution engine receiving a browser message that includes a commit transaction command, said cartridge execution engine sending a transaction control message to said transaction manager to cause said transaction manager to commit said transaction.

Claim 43

Dependent Claim 75 words

The system of claim 14 , wherein the step of said cartridge execution engine intercepting browser messages includes the step of said cartridge execution engine intercepting browser messages that include a rollback transaction command; and in response to said cartridge execution engine receiving a browser message that includes a rollback transaction command, said cartridge execution engine sending a transaction control message to said transaction manager to cause said transaction manager to roll back said transaction.

Claim 44

Dependent Claim 106 words

The method of claim 1 , further comprising the steps of: prior to intercepting browser messages directed to said cartridge, storing metadata that establishes a correlation between one or more transaction commands and one or more message items; in response to intercepting browser messages directed to said cartridge, comparing the message items that are within each browser message with said metadata to determine whether a particular transaction command needs to be executed; and if it is determined that a particular transaction command does need to be executed, including data within a transaction control message that will cause said transaction manager to perform the particular transaction command.

Claim 45

Dependent Claim 110 words

The computer readable medium, of claim 11 , further comprising instructions for performing the steps of: prior to intercepting browser messages directed to said cartridge, storing metadata that establishes a correlation between one or more transaction commands and one or message items; in response to intercepting browser messages directed to said cartidge, comparing the message items that are within each browser message with said metadata to determine whether a particular transaction command needs to be executed; and if it is determined that a particular transaction command does need to be executed, including data within a transaction control message that will cause said transaction manager to perform the particular transaction command.

Claim 46

Dependent Claim 106 words

The system of claim 14 , further comprising the steps of: prior to intercepting browser messages directed to said cartridge, storing metadata that establishes a correlation between one or more transaction commands and one or more message items; in response to intercepting browser messages directed to said cartridge, comparing the message items that are within each browser message with said metadata to determine whether a particular transaction command needs to be executed; and if it is determined that a particular transaction command does need to be executed, including data within a transaction control message that will cause said transaction manager to perform the particular transaction command.

Claim 47

Independent Claim 94 words

A method for executing a transaction that involves a series of operations, the method comprising the steps of: registering said transaction by storing metadata that establishes a mapping between transactions commands and message items; receiving a series of browser messages that request performance of said series of operations; in response to said series of browser messages, executing said series of operations as an atomic unit of work; and determining when to begin, commit and roll back said atomic unit of work based on message items in said series of browser messages and said metadata.

Claim 48

Independent Claim 94 words

A method for executing a transaction that involves a series of operations, the method comprising the steps of: registering said transaction by storing metadata that establishes a mapping between transactions commands and message items; receiving a series of browser messages that request performance of said series of operations; in response to said series of browser messages, executing said series of operations as an atomic unit of work; and determining when to begin, commit and roll back said atomic unit of work based on message items in said series of browser messages and said metadata.

Claim 49

Dependent Claim 42 words

The method of claim 44 , wherein the step of registering said transaction further comprises the step of storing metadata that establishes a belong-to-list, wherein the belong-to-list identifies a set of one or more cartridges that may participate in performing said transaction.

Claim 50

Dependent Claim 42 words

The method of claim 44 , wherein the step of registering said transaction further comprises the step of storing metadata that establishes a resource-list, wherein the resource-list identifies a set of one or more resources that are affected by performing the transaction.

Claim 51

Dependent Claim 43 words

The method of claim 44 , wherein the step of registering said transaction further comprises the step of storing metadata that establishes a cartridge name, wherein the cartridge name identifies a particular type of cartridges that may be used to perform the transaction.

Claim 52

Dependent Claim 40 words

The method of claim 44 , wherein the step of registering said transaction further comprises the step of storing metadata that establishes a transaction name, wherein the transaction name uniquely identifies a type of transaction relative to other transaction types.

Annuity Stage	Window Opens	Payment Deadline	Surcharge Period Until	Estimated Fee	Status
3.5 Years (Year 4)	2004-12-24	2005-06-25	2005-12-25	$2000.00	Window Closed / Lapsed
7.5 Years (Year 8)	2008-12-24	2009-06-25	2009-12-25	$3760.00	Window Closed / Lapsed
11.5 Years (Year 12)	2012-12-24	2013-06-25	2013-12-25	$7700.00	Window Closed / Lapsed

Method and apparatus for performing transactions in a stateless web environment which supports a declarative paradigm

Abstract

Inventors

Bibliographic Details

Claims Analysis

References Cited (Backward Citations)

USPTO Annuity & Maintenance Windows

Assigned Categories & Tags

Assign Category Tag