Board index Bitcoin Exchanges discussion Ideal exchange API methods

Ideal exchange API methods

Ideas, problems, research and discussion about Exchanges

Post 2014-03-19 15:55:18

Posts: 2
Location: Switzerland

Order Book: can set count limit for each asks and bids. So if user will choose small count of depth, it will be not just visual limitation, but received data will be much smaller.

Last Trades: each trade in request result should have timestamp, so we remember last received timestamp and new request will use this value as parameter to prevent receiving already received data.

HTTP gzip compression support: it will cause 5 time lower traffic, and users who have slow internet will receive much faster updates.

Return to Exchanges discussion

cron