IB Suggestions & Improvements

Quote from IBsoft:

....

2) Java is not slow. It was a few years ago, but it is not anymore. If there are performance issues w/ some of the TWS components, I would not blame it on Java, but on the implementation instead. Our charting is based on an open source code and it does have some performance issues; If you keep the number of open charts (especially those that update real-time w/ the new incoming data) to a reasonable number, the TWS performance should be fine. [/B]

I apologize if I offended anyone about the Java being slow comment, it was not my intention.

Can you direct me to a commercial Java application that represents a good implementation? I just want to see if it for myself.

Also, I think it was mentioned before, but being able to access TWS during at least one weekend day would be great.

Thanks
 
Quote from trada101:

I apologize if I offended anyone about the Java being slow comment, it was not my intention.

Can you direct me to a commercial Java application that represents a good implementation? I just want to see if it for myself.

Also, I think it was mentioned before, but being able to access TWS during at least one weekend day would be great.

Thanks

yes access to backfill and tws during the weekend would be great and the symbol TIKI added please especially for higher volume guys
 
Quote from dcraig:

This same problem has recurred with the 858 release. The Unix download marked as 858, isn't. It is 857. And now the 857 release will not startup on Linux. Again , the only way to get started is to use the java web start - this time for 858. Please keep the Unix releases in step with the Windows releases, or alternatively not break the the prior release.

Again, the latest TWS Unix release is not up to date. The download page shows the latest version as June 16, but the actual downloaded jar is:

Build 860.8, Jun 13, 2006 11:24:36 AM

This would be no big deal except for the fact that for reasons unknown the previous realease (Jun 13th) will not start up - it stalls on the splash screen with nothing useful in the log. As a speculative guess on where the problem is, I'd start with the new version available dialog being possibly underneath the splash screen or some dependency on what browser is configured. Anyway, it shouldn't be happening, and the Unix version should be up to date.

The current release starts correctly on Linux with Java web start, but this is a real nuisance as TWS cannot be autostarted or rather cannot be autostarted without writing a bit of extra code to first get it first by web start.

Please keep the Unix version up to date.
 
Quote from trada101:
Can you direct me to a commercial Java application that represents a good implementation? I just want to see if it for myself.


TWS (other than the charts, which are acknowledged to be resource hogs - they were not written by IB). Hard to know what you mean by "good".
 
Quote from IBsoft:

1) Our login is secure. The password is never transmitted between the TWS and the backend servers.

This security point may be worth highlighting in TWS documentation for users' peace of mind.
 
Quote from dcraig:

Again, the latest TWS Unix release is not up to date. The download page shows the latest version as June 16, but the actual downloaded jar is:

Build 860.8, Jun 13, 2006 11:24:36 AM

This would be no big deal except for the fact that for reasons unknown the previous realease (Jun 13th) will not start up - it stalls on the splash screen with nothing useful in the log. As a speculative guess on where the problem is, I'd start with the new version available dialog being possibly underneath the splash screen or some dependency on what browser is configured. Anyway, it shouldn't be happening, and the Unix version should be up to date.

The current release starts correctly on Linux with Java web start, but this is a real nuisance as TWS cannot be autostarted or rather cannot be autostarted without writing a bit of extra code to first get it first by web start.

Please keep the Unix version up to date.

I had this problem too whenever new releases were announced. After several chats with IB tech support, last week we finally got a fix that works for me: edit your jts.ini file in the directory IBJts to look something like this:

[communication]
checkversion=0

There may be other stuff there already; just add the checkversion line.

With this fix, I'm still using version 858.6 of May 1. Apparently version 860 won't read jts.ini anymore, so no idea what will happen when I upgrade to that version.
 
I would like to see a tighter spread on CHF/GBP. It is a good pair to trade but do you think we could get the spread down to two or three? Five to seven is a bit much, especially compared to the very tight spreads on other IB pairs
 
Quote from zf trader:

I would like to see a tighter spread on CHF/GBP. It is a good pair to trade but do you think we could get the spread down to two or three? Five to seven is a bit much, especially compared to the very tight spreads on other IB pairs

for that ib needs to get hold of new liq providers, and even that doesnt necessarly imply u get a better spread...these things are beyond ib control...me thinks.
 
Quote from hmartin:

I had this problem too whenever new releases were announced. After several chats with IB tech support, last week we finally got a fix that works for me: edit your jts.ini file in the directory IBJts to look something like this:

[communication]
checkversion=0

There may be other stuff there already; just add the checkversion line.

With this fix, I'm still using version 858.6 of May 1. Apparently version 860 won't read jts.ini anymore, so no idea what will happen when I upgrade to that version.

hmartin,

Thanks for the info.
 
Back
Top