Method of creating a tabular data stream for sending rows of data between client and server

• US 5,974,416 A
• Filed: 11/10/1997
• Issued: 10/26/1999
• Est. Priority Date: 11/10/1997
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Bennett, John G., Bath, Kamaljit S., Krishnaswamy, Raja, Tucker, Peter A., Anand, Thulusalamatom Krishnamurthi
• Primary Examiner(s): Kulik, Paul V.
• Assistant Examiner(s): Corrielus, Jean M.
• Application Number:
  US08/966,670
• Time in Patent Office: 715 Days
• Field of Search: 707/10, 707/3, 707/4, 707/100
• US Class Current: 709/203
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/26 Special purpose or proprietary protocols or architectures network applications for proprietary or special purpose networking environments H04L67/12
• CPC Class Codes: H04L 69/328 in the presentation layer [OSI layer 6]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: Y10S 707/922 Communications
• CPC Class Codes: Y10S 707/959 Network
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation

Abstract

A method and tabular data stream format is provided for the transmission of tabular data between a client process running on a client computer and a server process running on a server computer via a network such as the Internet. The tabular data stream format, called the Advanced Data TableGram (ADTG) format, is ideally suited for marshaling tabular data in both directions between a Web browser and a Web server. A Web browser query is processed by the Web server retrieving tabular data from a database and converting the data into a Rowset. The Rowset, in turn, is formatted into an ADTG message. The ADTG message includes a Header section, a HandlerOptions section, a Row section, and an End section. The Header section includes data representing global parameters for a tabular data stream. The Handler Options section contains data representing parameters for controlling the processing of the tabular data stream by a process receiving the tabular data stream. The Descriptors section includes data representing properties of the tabular data stream. The Row section includes data representing the properties of rows and values of the columns of the tabular data stream. The End section contains data that denotes the end of parts of an ADTG message, called resultsets, or the end of the entire ADTG message.

Claims

1. A computer-readable medium having stored thereon data formatted into a tabular data stream containing rows of data suitable for transmission between a client computer and a server computer through a network, said tabular data stream format comprising:

(a) a first section including data representing global parameters for said tabular data stream;

(b) a second section including data representing parameters for controlling the processing of the tabular data stream by a process receiving the tabular data stream;

(c) a third section including data representing properties of the tabular data stream;

(d) a fourth section including data representing the properties of rows and the values of columns of the tabular data stream; and

;

(e) a fifth section including data that represents the end of the tabular data stream.

2. A computer-readable medium having stored thereon data formatted into a tabular data stream suitable for transmission between a client computer and a server computer through a network as claimed in claim 1, wherein said first section comprises a Header section including a token having fields that contain said data representing global parameters for said tabular data stream.

3. A computer-readable medium having stored thereon data formatted into a tabular data stream suitable for transmission between a client computer and a server computer through a network as claimed in claim 1, wherein said second section comprises a HandlerOptions section including a token having fields that contain said data representing parameters for controlling the processing of the tabular data stream by a process receiving the tabular data stream.

4. A computer-readable medium having stored thereon data formatted into a tabular data stream suitable for transmission between a client computer and a server computer through a network as claimed in claim 1, wherein said third section comprises a Descriptors section including:

(a) a token having fields containing data representing the general properties of the tabular data stream;

(b) at least one token having fields containing data representing properties of tables from which the tabular data stream originated; and

(c) at least one token having fields containing data representing properties of columns of the tabular data stream.

5. A computer-readable medium having stored thereon data formatted into a tabular data stream suitable for transmission between a client computer and a server computer through a network as claimed in claim 4, wherein said Descriptors section also includes a token having fields containing data representing options/properties unique to the tabular data stream.

6. A computer-readable medium having stored thereon data formatted into a tabular data stream suitable for transmission between a client computer and a server computer through a network as claimed in claim 1, wherein said third section comprises a Descriptors section including a token having a field containing data that uniquely identifies cached data.

7. A computer-readable medium having stored thereon data formatted into a tabular data stream suitable for transmission between a client computer and a server computer through a network as claimed in claim 6, wherein said Descriptors section also includes a token having fields containing data representing options/properties unique to said cached data.

8. A computer-readable medium having stored thereon data formatted into a tabular data stream suitable for transmission between a client computer and a server computer through a network as claimed in claim 1, wherein said fourth section comprises a Row section including a token that identifies the nature of data rows contained in said tabular data stream.

9. A computer-readable medium having stored thereon data formatted into a tabular data stream suitable for transmission between a client computer and a server computer through a network as claimed in claim 8, wherein said data rows contained in said tabular data stream are identified as an original resultset row.

10. A computer-readable medium having stored thereon data formatted into a tabular data stream suitable for transmission between a client computer and a server computer through a network as claimed in claim 8, wherein said data rows contained in said tabular data stream are identified as an original base table row.

11. A computer-readable medium having stored thereon data formatted into a tabular data stream suitable for transmission between a client computer and a server computer through a network as claimed in claim 8, wherein said data rows contained in said tabular data stream are identified as a normalized row.

12. A computer-readable medium having stored thereon data formatted into a tabular data stream suitable for transmission between a client computer and a server computer through a network as claimed in claim 1, wherein said fourth section comprises a Row section including a token that identifies a data row contained in said tabular data stream as delete type data.

13. A computer-readable medium having stored thereon data formatted into a tabular data stream suitable for transmission between a client computer and a server computer through a network as claimed in claim 1, wherein said fourth section comprises a Row section including a token that identifies a data row contained in said tabular data stream as change type data.

14. A computer-readable medium having stored thereon data formatted into a tabular data stream suitable for transmission between a client computer and a server computer through a network as claimed in claim 1, wherein said fourth section comprises a Row section including a token that identifies a data row contained in said tabular data stream as insert type data.

15. A computer-readable medium having stored thereon data formatted into a tabular data stream suitable for transmission between a client computer and a server computer through a network as claimed in claim 1, wherein said fourth section comprises a Row section including a token that identifies a data row contained in said tabular data stream as read/verify type data.

16. A computer-readable medium having stored thereon data formatted into a tabular data stream suitable for transmission between a client computer and a server computer through a network as claimed in claim 1, wherein said fifth section comprises an End section including a token that either establishes the end of a part of the tabular data stream or identifies the end of the entire tabular data stream.

17. A computer-readable medium having stored thereon data formatted into a tabular data stream suitable for transmission between a client computer and a server computer through a network as claimed in claim 1, wherein said third section comprises a Descriptor section including a 16-byte unique identifier.

18. A method of creating a tabular data stream for sending rows of data between a client computer and a server computer through a network, said method comprising:

(a) packaging data representing global parameters for the tabular data stream into a first section;

(b) packaging data representing parameters for controlling the processing of the tabular data stream by a process receiving the tabular data stream into a second section immediately following the first section;

(c) packaging data representing properties of the tabular data stream into a third section immediately following the second section;

(d) packaging data representing properties of rows and values of columns of the tabular data into a fourth section immediately following the third section; and

(e) packaging data representing an end of the tabular data stream into a fifth section immediately following the fourth section.

19. The method claimed in claim 18, wherein said first section comprises a Header section including a token having fields that contain said data representing global parameters for the tabular data stream.

20. The method claimed in claim 18, wherein said second section comprises a HandlerOptions section including a token having fields that contain data representing parameters for controlling the processing of the tabular data stream by a process receiving the tabular data stream.

21. The method claimed in claim 18, wherein said third section comprises a Descriptors section including:

(a) a token having fields containing data representing the general properties of the tabular data stream;

(b) at least one token having fields containing data representing properties of tables from which the tabular data stream originated; and

(c) at least one token having fields containing data representing properties of columns of the tabular data stream.

22. The method claimed in claim 21, wherein said Descriptors section also includes a token having fields containing data representing options/properties unique to the tabular data stream.

23. The method claimed in claim 18, wherein said third section comprises a Descriptors section including a token having a field containing data that uniquely identifies cached data.

24. The method claimed in claim 23, wherein said Descriptors section also includes a token having fields containing data representing options/properties unique to the tabular data stream.

25. The method claimed in claim 18, wherein said fourth section comprises a Row section including a token that identifies the nature of data rows contained in said tabular data stream.

26. The method claimed in claim 25, wherein said data rows contained in said tabular data stream are identified as original resultset row.

27. The method claimed in claim 25, wherein said data rows contained in said tabular data stream are identified as original base table row.

28. The method claimed in claim 25, wherein said data rows contained in said tabular data stream are identified as normalized row.

29. The method claimed in claim 18, wherein said fourth section comprises a Row section including a token that identifies a data row contained in said tabular data stream as delete type data.

30. The method claimed in claim 18, wherein said fourth section comprises a Row section including a token that identifies a data row contained in said tabular data stream as change type data.

31. The method claimed in claim 18, wherein said fourth section comprises a Row section including a token that identifies a data row contained in said tabular data stream as inert type data.

32. The method claimed in claim 18, wherein said fourth section comprises a Row section including a token that identifies a data row contained in said tabular data stream as read/verify type data.

33. The method claimed in claim 18, wherein said fifth section comprises an End section including a token that either establishes the end of a part of the tabular data stream or identifies the end of the entire tabular data stream.

34. A method of querying a database through a network, wherein the database is associated with a server computer running a server process, the server computer connected to, and in communication with, a client computer through a network, the method comprising the steps of:

(a) issuing, by a client process running on a client computer, a query for data from a database;

(b) sending the query from the client computer to the server computer;

(c) processing the query, by the server process running on the client computer, and retrieving rows of data satisfying the query from one or more tables of the database;

(d) forming a Rowset containing the retrieved rows and metadata concerning the retrieved rows;

(e) packaging the Rowset into a message comprising a tabular datastream format suitable for marshaling tabular data for transfer between the client computer and the server computer; and

(f) sending the message to the client computer.

35. The method of claim 34, wherein the tabular datastream format comprises:

(a) a first section including data representing global parameters for said tabular data stream;

(b) a second section including data representing parameters for controlling the processing of the tabular data stream by a process receiving the tabular data stream;

(c) a third section including data representing properties of the tabular data stream;

(d) a fourth section including data representing the properties of rows and the values of columns of the tabular data stream; and

(e) a fifth section including data that represents the end of the tabular data stream.

36. The method claimed in claim 35, wherein said first section comprises a Header section including a token having fields that contain said data representing global parameters for the tabular data stream.

37. The method claimed in claim 35, wherein said second section comprises a HandlerOptions section including a token having fields that contain data representing parameters for controlling the processing of the tabular data stream by a process receiving the tabular data stream.

38. The method claimed in claim 35, wherein said third section comprises a Descriptors section including:

(a) a token having fields containing data representing the general properties of the tabular data stream;

(b) at least one token having fields containing data representing properties of tables from which the tabular data stream originated; and

(c) at least one token having fields containing data representing properties of columns of the tabular data stream.

39. The method claimed in claim 38, wherein said Descriptors section also includes a token having fields containing data representing options/properties unique to the tabular data stream.

40. The method claimed in claim 35, wherein said third section comprises a Descriptors section including a token having a field containing data that uniquely identifies cached data.

41. The method claimed in claim 40, wherein said Descriptors section also includes a token having fields containing data representing options/properties unique to the tabular data stream.

42. The method claimed in claim 35, wherein said Row section includes a token that identifies a data row contained in said tabular data stream as delete type data.

43. The method claimed in claim 35, wherein said Row section includes a token that identifies a data row contained in said tabular data stream as change type data.

44. The method claimed in claim 35, wherein said fourth section comprises a Row section including a token that identifies a data row contained in said tabular data stream as insert type data.

45. The method claimed in claim 35, wherein said fourth section comprises a Row section including a token that identifies a data row contained in said tabular data stream as read/verify type data.

46. The method claimed in claim 35, wherein said fifth section comprises an End section including a token that either establishes the end of a part of the tabular data stream or identifies the end of the entire tabular data stream.

47. The method claimed in claim 35, wherein said fourth section comprises a Row section including a token that identifies the nature of data rows contained in said tabular data stream.

48. The method claimed in claim 47, wherein said data rows contained in said tabular data stream are identified as an original resultset row.

49. The method claimed in claim 47, wherein said data rows contained in said tabular data stream are identified as an original base table row.

50. The method claimed in claim 47, wherein said data rows contained in said tabular data stream are identified as a normalized row.

51. The method of claim 34, further comprising the step of updating the database through the network, wherein the step of updating the database comprises the steps of:

(a) recreating, by the client process, the Rowset from the message;

(b) manipulating, by the client process, contents of the recreated Rowset;

(c) creating an updated Rowset containing updated rows and updated metadata concerning the updated rows resulting from manipulating the contents of the recreated Rowset;

(d) packaging the updated Rowset into a message comprising a tabular datastream format suitable for marshaling tabular data for transfer between the client computer and the server computer; and

(e) sending the message to the server computer;

(f) recreating, by the server process, the updated Rowset from the message; and

(g) updating the database with the updated Rowset.

52. A computer-readable medium having computer-executable instructions for performing the steps of:

(a) issuing, by a client process running on a client computer, a query for data from a database;

(b) sending the query from the client computer to the server computer;

(c) processing the query, by the server process running on the client computer, and retrieving rows of data satisfying the query from one or more tables of the database;

(d) forming a Rowset containing the retrieved rows and metadata concerning the retrieved rows;

(e) packaging the Rowset into a message comprising a tabular datastream format suitable for marshaling tabular data for transfer between the client computer and the server computer; and

(f) sending the message to the client computer.

53. A method of transmitting computer-executable instructions for performing the steps of:

(a) issuing, by a client process running on a client computer, a query for data from a database;

(b) sending the query from the client computer to the server computer;

(c) processing the query, by the server process running on the client computer, and retrieving rows of data satisfying the query form one or more tables of the database;

(d) forming a Rowset containing the retrieved rows and metadata concerning the retrieved rows;

(e) packaging the Rowset into a message comprising a tabular datastream format suitable for marshaling tabular data for transfer between the client computer and the server computer; and

(f) sending the message to the client computer.