IB Suggestions & Improvements

The good - the API GetHistory allows you to request 1 day bars.

The bad - Can only request back to March, 2005

The ugly - Can only request 5 days of data.

5 days of data for 1 day bars seems basically useless except maybe for figuring out pivots in the past week.

Suggestion for Improvement - Allow request for 10 years of 1 day bar data. It would not be bandwidth intensive since 10 years of EOD data would be about the same thing as 5 days of 1 minute intraday data. While doing that - remember to include basic info like Split and Dividend flags
 
Hi Ib,

Coming back to your very interesting FIX solution available for both trading and data, how do you connect? You mention CTCI: Computer-To-Computer Interface. Do you have any specs on which interfaces are admissible for a hookup to Ib? Can this be done via a cable connection Internet ISP? Do you also have a simulator for testing purposes?

Thank you Ib,
nono
 
Here is an idea that might work for both data mining whiners and bandwidth conserving provider: Time the forced logoff (the one currently around midnight US ET) to be between 5pm and 6pm ET.

It appears that the fewest number of "US most actively traded" instruments are in fact tradeable at that time, in contrast to Midnight when virtually all the Globex markets are active.

Additionally, the load from requests for backfill should be diminished as there will be no data lost as nothing (or at most, very little) has traded.

I don't trade the Asian markets so don't know their most active time. However, perhaps the Asia servers could have a different forced shutdown time.

The point being, there is an inconvenience regardless of when the forced shutdown happens, so why not tailor the shutdown time to a logical trading/client time rather than the traditional IT time.

best regards,
Ana Maria
 
Quote from amg:

Here is an idea that might work for both data mining whiners and bandwidth conserving provider: Time the forced logoff (the one currently around midnight US ET) to be between 5pm and 6pm ET.

Ana Maria
More...

great suggestion! 530pm - 6pm est is deadsville.
 
Quote from def:

perhaps true but I'd venture to guess that 99.9% of those complaining about the 1 logout per day are mining for data as opposed to running automated systems. more importantly, the log out is a security measure.
More...

Def,

I use esignal for my data. I have a dedicated machine with TWS and esignal open 24 hours a day. I don't mine IB data.

I fail to see how the security of my account is at any more at risk if I log in manually or a program logs me in automatically.

In the end, TWS is open for the same amount of time. If someone hacks my computer or uses a keylogger, they will capture my password and login details anyway.

If you are worried about customers mining data, then don't offer it or charge them for it.

Runningbear
 
Quote from Runningbear:

Def,

I use esignal for my data. I have a dedicated machine with TWS and esignal open 24 hours a day. I don't mine IB data.

I fail to see how the security of my account is at any more at risk if I log in manually or a program logs me in automatically.

In the end, TWS is open for the same amount of time. If someone hacks my computer or uses a keylogger, they will capture my password and login details anyway.

If you are worried about customers mining data, then don't offer it or charge them for it.

Runningbear
More...

Mining data is not the key issue - keep in mind that we have had a forced logout since inception. Note though that the number of requests to abolish the forced logout have increased lately. A case can be made for both sides of the security argument and as I mentioned i wouldn't rule anything out going forward. for now, if we are going to err, we will err on the side of caution. there have been some good suggestions which will be taken under consideration.

5:30-6 PM? We are talking about two different items. the first is the daily reset. the second is the forced log off.
Note at 5:30-6PM coincides with the Australian open for half the year and US stocks trade after hours till 8 PM. Furthermore, there are literally thousands of things going on behind the scenes which simply aren't ready for production by that time.

I would like to point out that the daily reset only lasts about 5 minutes now and you don't have to logoff during that period. the auto-logoff time can be adjusted to a time more convenient.
 
You could set up the forced log-offs for those internet connects which were not SSL connections. I haven't looked but I assume that if I use a SSL logon the entire session is running secure. You could optionalize forced logoffs on the secure sessions at the customer's discretion.

It is highly unlikely that a secure link would get hijacked. The way you guys hold up incoming and outgoing ACH fund transfers for what seems like weeks in the name of security should be enough to provide a lot of protection. A secure link just leaves the user's computer as the only way into the system. Your tokening approach to changing addresses, passwords, etc., provides security against everything except bogus trading. If one of your customers leaves his passwords for his email, bank accounts, and IB account info all over his\her machine location the forced daily logon is next to worthless.
 
Quote from def:


I would like to point out that the daily reset only lasts about 5 minutes now and you don't have to logoff during that period. the auto-logoff time can be adjusted to a time more convenient.
More...


thanks didn't know that.
 
This may be a crazy idea but here goes...

I know that IB is working on improvements and additions to its technology and platform all the time. Could we, your clients, be put in charge of setting the priorities?

I mean, give us transparency on the list of things you're working on and let us vote to determine which we want now and which we would like later.

I know you have polls and such, but that's not what I'm talking about. Polls are about one specific improvement. I'm talking about the whole list that is on the table at any one time (atleast the part which can be made public).

What do you others think?
 
Quote from Babak:

This may be a crazy idea but here goes...

I know that IB is working on improvements and additions to its technology and platform all the time. Could we, your clients, be put in charge of setting the priorities?

I mean, give us transparency on the list of things you're working on and let us vote to determine which we want now and which we would like later.

I know you have polls and such, but that's not what I'm talking about. Polls are about one specific improvement. I'm talking about the whole list that is on the table at any one time (atleast the part which can be made public).

What do you others think?
More...

a noble idea but we aren't a democracy and wouldn't want to show our playbook to the competition.
 
You must log in or register to reply here.
Back
Top