New IB Features
- Thread starter def
- Start date
TWS API is fantastic.
However ive found many bugs.
One i got today, like if i fire 20 related (attached) orders at TWS
from Java one after the other, TWS just cant handle it, and i see
NullPointer errors in TWS standard output.
Because they are being sent so fast, they get out of order
when TWS forwards them simultaneously to the
server and the attached order seem to get transmitted before
the parent orders.
I work around by putting a sleep of half a second between each
order i send to TWS.
So it works but doesnt fill me with 100% confidence...
But id rather have a flakely API than no API..
However ive found many bugs.
One i got today, like if i fire 20 related (attached) orders at TWS
from Java one after the other, TWS just cant handle it, and i see
NullPointer errors in TWS standard output.
Because they are being sent so fast, they get out of order
when TWS forwards them simultaneously to the
server and the attached order seem to get transmitted before
the parent orders.
I work around by putting a sleep of half a second between each
order i send to TWS.
So it works but doesnt fill me with 100% confidence...
But id rather have a flakely API than no API..
Im sure it can handle 50 a second normally.
But when i send 10, each with 2 attached orders (say a stop and
limit). Then i think sometimes the stop and limits get sent
before the parent order has been acknowleged by the IB
server.
Seems that TWS is being too eager to get all the orders executed, when it should be waiting a bit by itself.
I will write some code to reproduce this if IB cant do it.
thanks - have enjoyed having the RT scanner in TWS. Its a very useful feature.
My only question is :
Why don't you separate API and TWS GUI so that user only using API to trade are not obliged to load the TWS GUI too ?
A small client + a GUI would be better than the existing TWS architecture ?
It could be as simple as keeping the existing login screen but allowing a checkbox on the logging screen for not loading the UI.
That parameter would also be available in the INI file so that a script can edit it. An Autologin parameter in the INI file would be good too (if it exists I don't know it , I only know the one for login / password prefilling)
When not loading the UI, the memory & CPU used would be of course far lower.
This is a must for people only using IB's API for graphs, and trading via 3rd party tools.
Why don't you separate API and TWS GUI so that user only using API to trade are not obliged to load the TWS GUI too ?
A small client + a GUI would be better than the existing TWS architecture ?
It could be as simple as keeping the existing login screen but allowing a checkbox on the logging screen for not loading the UI.
That parameter would also be available in the INI file so that a script can edit it. An Autologin parameter in the INI file would be good too (if it exists I don't know it , I only know the one for login / password prefilling)
When not loading the UI, the memory & CPU used would be of course far lower.
This is a must for people only using IB's API for graphs, and trading via 3rd party tools.
That is still not sufficient when you don't get the Account and Budget and Positions through the FIX-protocol......If market-date is added it is a good step forward (although this is still not presented on the website)...but we can not use ButtonTrader to connect to FIX (and bypass TWS) when we miss Account/budget/positions....
Hope it may change some time in future.
hello steve , def , and all IB support staff
when I log in to my TWS ( ver 848.9 )
I do not show any menu pages from earlier version
and am clueless as to what happened to the old pages I had saved .
is this something tech support can help guide me though or even cust support helpdesk ?
thanks again
when I log in to my TWS ( ver 848.9 )
I do not show any menu pages from earlier version
and am clueless as to what happened to the old pages I had saved .
is this something tech support can help guide me though or even cust support helpdesk ?
thanks again