Gap detector detecting gaps between transactions transmitted by clients and transactions processed by servers

• US 6,871,293 B2
• Filed: 08/07/2001
• Issued: 03/22/2005
• Est. Priority Date: 08/07/2001
• Status: Active Grant

• Current Assignee: CGI Technologies and Solutions Incorporated (CGI Group)
• Original Assignee: American Management Systems, Incorporated (CGI, Inc.)
• Inventors: Singh, Ashish, Rothstein, Richard Stephen, Simmons, James Edward, Bomfim, Joanes DePaula
• Primary Examiner(s): Iqbal, Nadeem
• Application Number:
  US09/922,698
• Publication Number:
  US 20030033554A1
• Time in Patent Office: 1,323 Days
• Field of Search: 714/4, 714/18, 714/20, 714/39, 714/43, 714/48, 714/818, 714/821, 714/15, 714/16, 714/17, 714/21, 714/27, 714/49, 709/102, 709/104, 709/206
• US Class Current: 714/4.4
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A client/server computer architecture having a gap detector detecting gaps in sequence numbers of transactions transmitted by clients and processed by servers. When a gap is detected to thereby indicate that a respective transaction was transmitted but not processed, the client that originally transmitted the transaction is notified so that the client can retransmit the transaction.

Claims

1. An apparatus comprising:

a gap detector receiving server information indicating which transactions transmitted by a client to a server through a computer communication network were processed by the server, and detecting gaps between the transmitted transactions and the processed transactions from the received server information, the gaps thereby indicating which of the transmitted transactions were not processed by the server;

a control information adder adding control information to each transaction transmitted by the client, the control information including a sequence number of the transmitted transaction; and

a control information remover removing control information from transmitted transactions received by the server to allow the server to process the transaction without the control information, the removed control information being used to determine the server information.

2. An apparatus as in claim 1, wherein, when a gap is detected by the gap detector to thereby indicate that a transmitted transaction was not processed by the server, the client is notified that the transmitted transaction was not processed and then the client retransmits the transaction.

3. An apparatus as in claim 1, wherein the gap detector receives client information from the client indicating which transactions were transmitted by the client, and detects gaps between the transmitted transactions and the processed transactions in accordance with the received client information and the received server information, the apparatus further comprising:

a first file in which the client stores the client information, the gap detector accessing the first file to thereby receive the client information; and

a second file in which server stores the server information, the gap detector accessing the second file to thereby receive the server information.

4. An apparatus as in claim 3, further comprising:

a third file in which the gap detector stores information indicating that a gap has been detected, the client accessing the third file to thereby be notified that a gap has been.

5. An apparatus as in claim 2, further comprising:

a first file in which server stores the server information, the gap detector

accessing the first file to thereby receive the server information; and

a second file in which the gap detector stores information indicating that a gap has been detected and indicating which of the transmitted transactions were not processed, the client accessing the second file to thereby be notified which transmitted transactions were not processed.

6. An apparatus as in claim 2, further comprising:

a log in which the client logs transmitted transactions, the client accessing the log to retrieve and retransmit a respective transaction when the client is notified that the transmitted transaction was not processed.

7. An apparatus comprising:

a client adding sequence numbers to transactions, and then transmitting the transactions with the added sequence numbers;

a transaction log in which the client logs the transmitted transactions;

a server receiving the transmitted transactions with the added sequence numbers, removing the sequence numbers, and then processing the transactions with the removed sequence numbers;

a first file in which the server stores sequence numbers of transactions processed by the server;

a gap detector accessing the first file to receive the sequence numbers of the processed transactions, and, from the received sequence numbers, detecting whether there is a gap between the sequence numbers of the transmitted transactions and the sequence numbers of processed transactions, a gap indicating that at least one transmitted transaction was not processed; and

a second file in which the gap detector stores information indicating the sequence number for each of said at least one transmitted transaction, wherein the client accesses the second file to thereby be notified of the sequence number of each of said at least one transmitted transaction, and then accesses the transaction log to obtain and then retransmit each of said at least one transmitted transaction.

8. An apparatus comprising:

a gap detector receiving server information indicating which transactions transmitted by clients to servers through a computer communication network were processed by the servers, and detecting gaps between the transmitted transactions and processed transactions from the received server information, the gaps thereby indicating which of the transmitted transactions were not processed by the servers, wherein

each client includes a control information adder adding control information to each transaction transmitted by the respective client, the control information including a sequence number of the transmitted transaction, and

each server includes a control information remover removing control information from transmitted transactions received by the respective server to allow the server to process the transaction without the control information, the removed control information being used to determine the server information.

9. An apparatus as in claim 8, wherein, when a gap is detected by the gap detector to thereby indicate that a respective transmitted transaction was not processed by a server, the client that originally transmitted the transaction is notified that the transmitted transaction was not processed and then the client retransmits the transaction.

10. An apparatus as in claim 8, further comprising:

server files in which the servers store the server information, the gap detector accessing the server files to thereby receive the server information.

11. An apparatus as in claim 10, further comprising:

a gap detector file in which the gap detector stores information indicating that a gap has been detected, the clients accessing the gap detector file to thereby be notified that a gap has been detected.

12. An apparatus as in claim 9, wherein the gap detector receives client information from the clients indicating which transactions were transmitted by the clients, and detects gaps between the transmitted transactions and the processed transactions from the received client information and the received server information, the apparatus further comprising:

client files in which the clients store the client information, the gap detector accessing the client files to thereby receive the client information;

server files in which servers store the server information, the gap detector accessing the server files to thereby receive the server information; and

a gap detector file in which the gap detector stores information indicating that a gap has been detected and indicating which of the transmitted transactions were not processed, the clients accessing the gap detector file to thereby be notified which transmitted transactions were not processed.

13. An apparatus as in claim 9, wherein

each client includes a log in which the respective client logs transactions transmitted by the client, the client accessing the log to retrieve and retransmit a respective transaction when the client is notified tat the transmitted transaction was not processed.

14. An apparatus comprising:

clients adding sequence numbers to transactions, and then transmitting the transactions with the added sequence numbers;

transaction logs in which the clients log the transmitted transactions;

servers receiving the transmitted transactions with the added sequence numbers, removing the sequence numbers, and then processing the transactions with the removed sequence numbers;

server files in which the servers store sequence numbers of transactions processed by the servers;

a gap detector accessing the server files to receive the sequence numbers of the processed transactions, and, from the received sequence numbers, detecting whether there is a gap between the sequence numbers of the transmitted transactions and the sequence numbers of processed transactions, a gap indicating that at least one transmitted transaction was not processed; and

a gap detector file in which the gap detector stores information indicating the sequence number for each of said at least one transmitted transaction, the clients accessing the gap detector file to thereby be notified of the sequence number of each of said at least one transmitted transaction,

wherein, when a respective client is notified of a sequence number of a transaction transmitted by the client, the client accesses one of the transaction logs to obtain and then retransmit the transaction.

15. An apparatus comprising;

clients each having a corresponding client ID, each client adding its client ID and a sequence number to transactions transmitted by the respective client;

transaction logs in which the clients log the transmitted transactions;

servers receiving the transmitted transactions with the added client IDs and sequence numbers, removing the client IDs and sequence numbers, and then processing the transactions with the removed client IDs and sequence numbers;

server files in which the servers store information indicating the client ID and sequence number of each transaction processed by the servers;

a detector accessing the server files to receive the stored information, and, from the received information, detecting transmitted transactions which were not processed; and

a detector file in which the detector stores information indicating the client ID and sequence number for each of the detected transactions, the clients accessing the detector file to thereby be notified of the client IDs and sequence numbers of the detected transactions,

wherein, when a respective client is notified of a sequence number of a transaction transmitted by the client, the client accesses one of the transaction logs to obtain and then retransmit the transaction.