Module krakenrs::ws [−][src]
Expand description
An interface for getting data from Kraken websockets API, while another thread manages the updates from the websockets connection.
This follows the pattern of bridging async code into a sync interface See also: https://tokio.rs/tokio/topics/bridging and the reqwest::blocking module
Structs
Add order request (websockets)
The state of the book for some asset pair
An entry in an order book
Configuration for private websockets feeds
A handle to Kraken websockets API feeds
A Kraken websockets api client
Configuration for the websocket connection and feeds to subscribe to
Order-description-info used in GetOpenOrders API
Order-info used in OpenOrders and QueryOrders APIs
A sink where the ws worker can put updates for subscribed data
Enums
Type (buy/sell) These are kebab-case strings in json
Possible WebSocket errors.
Possible miscellaneous info flags in Kraken. These are options in a comma-separated list
Possible order flags in Kraken WS API. These are options in a comma-separated list
Possible order statuses in Kraken. These are kebab-case strings in json
Possible order types in Kraken. These are kebab-case strings in json
Possible subscription status types in Kraken WS api
Possible system status types in Kraken WS api
Type Definitions
User-reference id’s are signed 32-bit in kraken json api