System and method for coalescing market data at a client device

• US 7,742,962 B1
• Filed: 05/02/2006
• Issued: 06/22/2010
• Est. Priority Date: 06/26/2002
• Status: Active Grant

• Current Assignee: Trading Technologies International, Inc.
• Original Assignee: Trading Technologies International, Inc.
• Inventors: Singer, Scott F.
• Primary Examiner(s): Dass; Harish T.
• Application Number:
  US11/416,405
• Time in Patent Office: 1,512 Days
• Field of Search: 705 35- 37, 709/219, 709/203, 709/217, 707/217, 345/418, 340/10.31, 715/762, 370/326
• US Class Current: 705/35
• CPC Class Codes: G06Q 20/042 characterized in that the payment protocol involves at least one cheque
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/04 Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
• CPC Class Codes: G06Q 40/06 Asset management; Financial planning or analysis

Abstract

A client device coalesces data received from an exchange, and provides a client application such as a graphical user interface with the opportunity to process fewer, but up-to-date, data updates from an exchange when a large volume of prices becomes available. Accordingly, the trader can be assured of receiving updated information that are fed to the client applications at a rate that is cohesive with that client device'"'"'s processing speed.

Claims

1. A method for coalescing market data at a client device, the method comprising the steps of:

receiving by a client device in a first thread at a client device a first market data update for a tradeable object from an electronic exchange;

storing by the client device the first market data update in a shared data structure, wherein the shared data structure is shared between the first thread and a second thread;

notifying by the client device a graphical user interface running in the second thread of the first market data update;

receiving by the client device in the first thread at the client device a second market data update for the tradeable object from the electronic exchange subsequent to the step of notifying;

replacing by the client device the first market data update in the shared data structure with the second market data update before the first market update is received by the graphical user interface; and

retrieving by the client device the second market data update from the shared data structure by the graphical user interface responsive to the step of notifying.

2. The method of claim 1, wherein the shared data structure includes a plurality of fields, wherein the first market data update is stored in one of the plurality of fields.

3. The method of claim 1, wherein the first thread is a communication thread.

4. The method of claim 1, wherein the second thread is a graphical user interface.

5. A method for coalescing market data, the method including:

receiving by a client device at an API running in an API thread of the client device a first market data update for a tradeable object from an electronic exchange;

storing by the client device the first market data update in a shared data structure, wherein the shared data structure is shared between at least the API thread and a graphical user interface thread, wherein the graphical user interface thread is running a graphical user interface for the client device;

providing by the client device a notification to the graphical user interface that the shared data structure includes an update;

receiving by the client device at the API running in the API thread at least one subsequent market data update for the tradeable object from an electronic exchange, wherein the subsequent market data update is received subsequent to providing the notification; and

overwriting by the client device the first market data update with the at least one subsequent market data update before the first market update is received by the graphical user interface to create a coalesced market data update until the graphical user interface indicates to the API running in the API thread that the graphical user interface has retrieved the coalesced market data update responsive to the notification.

6. The method of claim 5, further including clearing the shared data structure after the graphical user interface has retrieved the coalesced market data update.

7. The method of claim 5, further including:

receiving at the API running in the API thread a second market data update after the graphical user interface has retrieved the coalesced market data update;

storing the second market data update in the shared data structure; and

providing a second notification to the graphical user interface that the shared data structure includes a second update.

8. The method of claim 5, wherein the shared data structure includes a plurality of fields, wherein the first market data update and the at least one subsequent market data update are associated with one of the plurality of fields.

9. The method of claim 5, wherein the notification to the graphical user interface includes setting a flag.

10. The method of claim 5, wherein the notification to the graphical user interface includes placing a message in a message queue for the graphical user interface.

11. The method of claim 10, wherein a second notification is not sent to the graphical user interface if a pending notification is in the message queue for the graphical user interface.

12. The method of claim 5, wherein the first market data update and the at least one subsequent market data update are for a price of the tradeable object.

13. The method of claim 5, wherein the first market data update and the at least one subsequent market data update are for an order of the tradeable object.

14. The method of claim 5, wherein the first market data update and the at least one subsequent market data update are for a fill of the tradeable object.

15. The method of claim 5, wherein the first market data update and the at least one subsequent market data update are for a last traded price of the tradeable object.

16. The method of claim 5, wherein the first market data update and the at least one subsequent market data update are for a last traded quantity of the tradeable object.

17. The method of claim 5, wherein the first market data update and the at least one subsequent market data update are for an inside market of the tradeable object.

18. The method of claim 5, wherein the first market data update and the at least one subsequent market data update are for a settlement price of the tradeable object.