Transactional and non-transactional data for maintaining session state

Patent metadata

Field	Value
Publication number	US-9591103-B2
Application number	US-201514748451-A
Country	US
Kind code	B2
Filing date	Jun 24, 2015
Priority date	Sep 9, 2011
Publication date	Mar 7, 2017
Grant date	Mar 7, 2017

Abstract

Transactional and non-transactional data for maintaining session state is described. In a session, a server instance receives, from a client, a request to execute transactional commands and non-transactional commands. The server instance sends at least one first directive executable at the client to store, in a first set of information, one or more first items representing one or more particular transactional commands that are open but not yet committed. The first set of information is maintained separately from a second set of information including one or more second items representing one or more particular non-transactional commands that have been processed. Based on committing one or more particular transactional commands, the server instance sends at least one second directive executable at the client to purge, from the first set of information, the one or more first items without purging, from the second set of information, the one or more second items.

First claim

What is claimed is:

1. A method comprising:
a server instance receiving, from a client in a session between the server instance and the client, a request to execute:
one or more transactional commands that, when executed, cause changes to a database, and
one or more non-transactional commands that, when executed, do not cause changes to the database;

the server instance sending, to the client, at least one first directive instructing the client to store one or more first items representing one or more particular transactional commands that are open but not yet committed in the session in a first set of information and to store one or more second items representing one or more particular non-transactional commands that have been processed in the session in a second set of information;
determining that the one or more particular transactional commands have committed in the session; and
based at least in part on determining that the one or more particular transactional commands have committed in the session, the server instance sending, to the client in the session, at least one second directive instructing the client to purge, from the first set of information, the one or more first items that represent the one or more particular transactional commands without purging, from the second set of information, the one or more second items that represent the one or more particular non-transactional commands;
wherein the method is performed by one or more computing devices.

2. The method of claim 1 , further comprising:
determining that the request has completed in the session;
based at least in part on determining that the request has completed in the session, the server instance sending, to the client in the session, a third directive instructing the client to purge, from the second set of information, the one or more second items that represent the one or more particular non-transactional commands.

3. The method of claim 2 , wherein the third directive instructs the client to purge, from the first set of information, the one or more first items that represent any transactional command.

4. The method of claim 1 , wherein the at least one first directive comprises at least one directive instructing the client to store, in the second set of information, the one or more second items that represent the one or more particular non-transactional commands.

5. The method of claim 4 , further comprising:
determining that the particular one or more non-transactional commands have been processed in the session;
based at least in part on determining that the particular one or more non-transactional commands have been processed in the session, the server instance sending, to the client in the session, one or more directives instructing the client to maintain, in the second set of information, the one or more second items that represent the one or more particular non-transactional commands.

6. The method of claim 1 ,
wherein a first data structure is used to store the first set of information is stored; and
wherein a second data structure is used to store the second set of information.

7. The method of claim 6 , wherein the first data structure is a first queue and the second data structure is a second queue.

8. The method of claim 1 ,
wherein the session has a static state indicating that session state changes for the session occur as part of session initialization or outside of any transaction; and
wherein the server instance sends the at least one second directive in response to committing any transaction in the session.

9. The method of claim 1 , further comprising:
detecting that a transaction in the request sets a non-transactional session state;
determining whether later commands in the request use the non-transactional session state;
if it is determined that later commands do not use the non-transactional session state, after committing the transaction, the server instance sending, to the client in the session, at least one directive instructing the client to purge, from the first set of information and the second set of information, the one or more first items that represent the one or more particular transactional commands and the one or more second items that represent the one or more particular non-transactional commands; and
if it is determined that later commands use the non-transactional session state, after committing the transaction, the server instance sending, to the client in the session, a directive instructing the client to purge, from the first set of information, the one or more first items that represent the one or more particular transactional commands.

10. The method of claim 1 , further comprising:
the server instance detecting that one or more transactions of the request are committed;
the server instance detecting that later commands use a session state that was changed during the one or more committed transactions of the request but was not persisted by the one or more transactions;
in response, the server instance sending, to the client in the session, a third set of information describing one or more commands that change the session state without repeating the one or more committed transactions; and
the server instance sending, to the client in the session, a directive instructing the client to purge from the first set of information, the one or more first items that represent the one or more particular transactional commands.

11. One or more non-transitory storage media storing one or more sequences of instructions which, when executed by one or more computing devices, cause:
a server instance receiving, from a client in a session between the server instance and the client, a request to execute:
one or more transactional commands that, when executed, cause changes to a database, and
one or more non-transactional commands that, when executed, do not cause changes to the database;

the server instance sending, to the client, at least one first directive instructing the client to store one or more first items representing one or more particular transactional commands that are open but not yet committed in the session in a first set of information and to store one or more second items representing one or more particular non-transactional commands that have been processed in the session in a second set of information;
determining that the one or more particular transactional commands have committed in the session; and
based at least in part on determining that the one or more particular transactional commands have committed in the session, the server instance sending, to the client in the session, at least one second directive instructing the client to purge, from the first set of information, the one or more first items that represent the one or more particular transactional commands without purging, from the second set of information, the one or more second items that represent the one or more particular non-transactional commands.

12. The one or more non-transitory storage media of claim 11 , wherein the one or more sequences of instructions include instructions which, when executed by the one or more computing devices, cause:
determining that the request has completed in the session;
based at least in part on determining that the request has completed in the session, the server instance sending, to the client in the session, a third directive instructing the client to purge, from the second set of information, the one or more second items that represent the one or more particular non-transactional commands.

13. The one or more non-transitory storage media of claim 12 , wherein the third directive instructs t

Assignees

• Oracle Int Corp

Inventors

• Neel Kevin S
• Colrain Carol L
• Surber Douglas N
• Ikeda Nancy R
• Roesch Stefan Heinrich
• Zhou Tong
• De Lavarene Jean

Classifications

• H04L67/142

  Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms · CPC title

• G06F9/466 Primary

  Transaction processing · CPC title

• G06F11/1443

  Transmit or communication errors · CPC title

• G06F11/1474

  in transactions (updating of structured data in databases G06F16/23) · CPC title

• H04L67/148

  Migration or transfer of sessions · CPC title