You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
IB Suggestions & Improvements
- Thread starter Babak
- Start date
there's a new feature on the latest tws preventin' orders to go trough immediately on booktrader: a pop up comes up after i place an order sayin: "ARE YOU SURE YOU WANT TO TRANSMIT THIS ORDER"?
if i dont want to see that window again, i have to check the "yes" box, therefore allowin' the order to go trough: after i click on "CHECK HERE IF YOU DONT WANT TO SEE THIS MESSAGE AGAIN", on the window i dont have anymore the option of rejectin' the order by checkin' "no" as answer to the first message 'cause the "no" box becomes blank, leavin' me no choice but to check "yes" if i want to get rid of the pop up.
it is very annoyin' and potentially dangerous to have to send a fake order every mornin' in order to disactivate the alert. would be great if u can get rid of this new feature.
thx
if i dont want to see that window again, i have to check the "yes" box, therefore allowin' the order to go trough: after i click on "CHECK HERE IF YOU DONT WANT TO SEE THIS MESSAGE AGAIN", on the window i dont have anymore the option of rejectin' the order by checkin' "no" as answer to the first message 'cause the "no" box becomes blank, leavin' me no choice but to check "yes" if i want to get rid of the pop up.
it is very annoyin' and potentially dangerous to have to send a fake order every mornin' in order to disactivate the alert. would be great if u can get rid of this new feature.
thx
My Suggestions:
1. Remove that silly SSL checkbox on the Login screen, all logins should be SECURE! This is not an email account, it's one of the biggest financial accounts I have, why would there be an non secure way to login????
2. Port TWS into a fast high performance langugage like C++. This Java isn't cutting it, slow and memory intensive. I'm running a 2.8ghz Dual core computer and it runs so sluggish. In contrast on the same machine Cybertrader is very snappy and everything is almost instantaneous. I'm running it with like 20 charts and it only takes up 50MB of ram and runs like a speed demon. IB takes up almost 80MB with 1 chart open and I feel like I'm running a web browser application. It feels almost as sluggish as Ameritrade's command center which is a web app.
3. Have a floating tool bar for quick order entries. Something small so you do not have to have have the entire TWS window open. That way I can be looking at my Quotetracker charts and submit the order through TWS.
But the most important are #1 and #2, make all TWS communications SECURE and speed up the application response time.
1. Remove that silly SSL checkbox on the Login screen, all logins should be SECURE! This is not an email account, it's one of the biggest financial accounts I have, why would there be an non secure way to login????
2. Port TWS into a fast high performance langugage like C++. This Java isn't cutting it, slow and memory intensive. I'm running a 2.8ghz Dual core computer and it runs so sluggish. In contrast on the same machine Cybertrader is very snappy and everything is almost instantaneous. I'm running it with like 20 charts and it only takes up 50MB of ram and runs like a speed demon. IB takes up almost 80MB with 1 chart open and I feel like I'm running a web browser application. It feels almost as sluggish as Ameritrade's command center which is a web app.
3. Have a floating tool bar for quick order entries. Something small so you do not have to have have the entire TWS window open. That way I can be looking at my Quotetracker charts and submit the order through TWS.
But the most important are #1 and #2, make all TWS communications SECURE and speed up the application response time.
Quote from trada101:
1. Remove that silly SSL checkbox on the Login screen, all logins should be SECURE! This is not an email account, it's one of the biggest financial accounts I have, why would there be an non secure way to login????
In general, removing options is a bad idea. It often results in having to put the option back again because someone needs it.
Specifically, there have been times when the SSL server-side platform has problems, and users have needed to un-check the box to log in. If I remember correctly, there is still some sort of encryption used when it's unchecked - it's just not as strong. If you look back to the original arguments for/against adding SSL, I think you'll see that the case was just barely made for implementing it to begin with.
1. Remove that silly SSL checkbox on the Login screen, all logins should be SECURE! This is not an email account, it's one of the biggest financial accounts I have, why would there be an non secure way to login????
In general, removing options is a bad idea. It often results in having to put the option back again because someone needs it.
Specifically, there have been times when the SSL server-side platform has problems, and users have needed to un-check the box to log in. If I remember correctly, there is still some sort of encryption used when it's unchecked - it's just not as strong. If you look back to the original arguments for/against adding SSL, I think you'll see that the case was just barely made for implementing it to begin with.
My point was really not about SSL, it's about security. I'd expect the strongest security measures for such an important financial account. I don't want something "not as strong" as SSL. I was something stonger! But seriously, why don't they just implement a robust security system? What gives? Technology limitations?
Quote from alanm:
Quote from trada101:
1. Remove that silly SSL checkbox on the Login screen, all logins should be SECURE! This is not an email account, it's one of the biggest financial accounts I have, why would there be an non secure way to login????
In general, removing options is a bad idea. It often results in having to put the option back again because someone needs it.
Specifically, there have been times when the SSL server-side platform has problems, and users have needed to un-check the box to log in. If I remember correctly, there is still some sort of encryption used when it's unchecked - it's just not as strong. If you look back to the original arguments for/against adding SSL, I think you'll see that the case was just barely made for implementing it to begin with.
Our login procedure is absolutely secure in any case. SSL makes sense if you worry about somebody listening your channel and trying to figure out what exactly you are doing. For overwhelming majority it does not matter. SSL is not absolutely free in sense of time and resources. If you do not feel like your trading strategy is a real treasure or your financial information is not super-valuable, SSL is an unnecessary burden.
Why you think that SSL is not enough?
Why you think that SSL is not enough?
But what if I do feel like
"your trading strategy is a real treasure or your financial information is not super-valuable, SSL is an unnecessary burden".
Uh, but I do feel it is super valuable, that's why I want the strongest protection. I actually expect it.
Isn't one of the main purposes of encryption to prevent someone who may be listening or spying from reading the information?
I'm not a security expert but when I get SSL level encryption with my free Yahoo email automatically (no option here) but I can't get it by default with my day trading broker, that's not right. There are times when I've experienced login problems when using SSL did not work. It happens enough to be a concern.
"your trading strategy is a real treasure or your financial information is not super-valuable, SSL is an unnecessary burden".
Uh, but I do feel it is super valuable, that's why I want the strongest protection. I actually expect it.
Isn't one of the main purposes of encryption to prevent someone who may be listening or spying from reading the information?
I'm not a security expert but when I get SSL level encryption with my free Yahoo email automatically (no option here) but I can't get it by default with my day trading broker, that's not right. There are times when I've experienced login problems when using SSL did not work. It happens enough to be a concern.
Quote from ids:
Our login procedure is absolutely secure in any case. SSL makes sense if you worry about somebody listening your channel and trying to figure out what exactly you are doing. For overwhelming majority it does not matter. SSL is not absolutely free in sense of time and resources. If you do not feel like your trading strategy is a real treasure or your financial information is not super-valuable, SSL is an unnecessary burden.
Why you think that SSL is not enough?
Quote from trada101:
My Suggestions:
1. Remove that silly SSL checkbox on the Login screen, all logins should be SECURE! This is not an email account, it's one of the biggest financial accounts I have, why would there be an non secure way to login????
2. Port TWS into a fast high performance langugage like C++. This Java isn't cutting it, slow and memory intensive. I'm running a 2.8ghz Dual core computer and it runs so sluggish. In contrast on the same machine Cybertrader is very snappy and everything is almost instantaneous. I'm running it with like 20 charts and it only takes up 50MB of ram and runs like a speed demon. IB takes up almost 80MB with 1 chart open and I feel like I'm running a web browser application. It feels almost as sluggish as Ameritrade's command center which is a web app.
3. Have a floating tool bar for quick order entries. Something small so you do not have to have have the entire TWS window open. That way I can be looking at my Quotetracker charts and submit the order through TWS.
But the most important are #1 and #2, make all TWS communications SECURE and speed up the application response time.
1) Our login is secure. The password is never transmitted between the TWS and the backend servers.
If you check the SSL checkbox, it will result in the whole order and execution traffic between the two points being encrypted by SSL.
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.