I was wondering if there was any hope that, at least for historical prices, that the prices returned would be shortened to their actual length in order to save bandwith?

I.e., if I connect to the history socket and request IBM, all the prices are like:

82.210000

That's 4 bytes of wasted bandwidth, both on your end and for everyone one of us.

At, say, 4 prices per line, that's 16 bytes. Over thousands of lines, that's a hundreds of thousands of wasted bytes. That _really_ cuts into bandwidth.

Any hope that you might consider shaving off the extra data and save us all some bandwidth, time, and memory?

Thanks.
Patrick

And while I'm on the topic of bandwidth, why not change the datetime format so that it is in numbers of seconds since epoch? Or something similar---

2005-07-19 12:12:12

is a real waste of bandwidth when that entry occurs on every single line, and you could just as easily use:

1121792574

Over the course of a day of trading, thats an absolute ton of wasted bandwidth...
Edited by squirlhntr on Jul 19, 2005 at 12:06 PM

unless of course that data isn't coming from you, but is a lengthened version of data coming from you, as altered by iqconnect after the fact....

is the data i read off the history and realtime sockets literal data from your system? or does the iqconnect exe/dll translate it into a longer form so that its easier for us to parse?
Edited by squirlhntr on Jul 19, 2005 at 10:23 PM

The data you see coming out of IQFeed is not what is being sent over the Internet. What is sent over the internet is much smaller than what you see. If you open IQConnect Manager, you will see that we display both Internet Bandwidth and Local Bandwidth statistics. You will see that the local bandwidth is much greater than was is actually sent over the net.

---

Jay Froscheiser
DTN - Trading Markets

Excellent!

Thanks.