Search results

The following explanation goes way beyond the scope I am comfortable discussing here; this one time I'll make an exception. --- We use TCP (aka stream) sockets to communicate between the TWS and the back-end servers. The connection between the two parties can get broken in two ways: a)...

simki, here is the followup: Currently, the simulated stops, trailing stops, stop limits, market-to-limit orders, good-after-time, good-till-time, good-till-date, gtc is done on the server to which you connect. The rest is done on the server local to the traded instrument .

Moderator, the purpose of this thread was to announce new TWS features. The thread turned into something else. Please consider closing it. Thank you.

Please check whether it does the same on the TWS BookTrader. If so, please PM "DAV". If not, you'll have to ask Ninja.

Please try running the latest beta. Is it still the same? If so, please PM "DAV".

We made the change when we introduced the 5-day backfills. Depending on the length of the time the user requests, we return the data with what we deem to be appropriate granularity. This is so as not to burden the back and from end processes and to keep the communication between the two to a...

Vanilla orders get sent to the US. I think the conditional/simulated orders depend on the order type. I'll clarify this a bit later. What happens to your order while HK is in "maintenance" depends on whether or not the order was sent to the US. A good news though is, that for those HK...

I am not aware of the difference between US/EUR and HK. Sorry.

Java. We now have the FIX over the internet solution. There would not be $1,500 per month minimum. We would more likely charge a lower, one time setup fee, but I will have to get back to you once we decide.

As a retail (a.k.a. cleared customer) aside from the web-trader and mobile-trader you have the following choices to connect to us: --- a) TWS and API for both order routing and market data. --- b) FIX for order routing. We run an application on your desktop which connects to...

Thank YOU for making it possible to fix them by providing failure specifics.

well said

here is how it works: (you can substitute different countries into my explanation, it still works the same) if you live in Asia and trade Asia you are best off connecting in Asia; if instead you connected trough USA, you would incur unnecessary Asia-USA-Asia delay if you live in Asia and...

yes

When your connectivity problems are solved, you trade again and you find a NEW case, please do send it. Thanks.

I do not work for the CS, hence I do not get paid for or can afford combing through lengthy audit-trails. All I asked for was a time-stamp of what you perceive to be a slow transaction. When your connectivity problems are solved and you find such a case, please do send it. Thank you.

I am still expecting to receive the audit-trail of a slow transaction.

There are no current plans to provide backfills of transactional data through the API.

Strange, it should handle 50 orders per second. Someone will get in touch w/ you.

Thank you for your PM. We were able to reproduce in-house that after the disconnect the market-depth does not properly re-cover. Should be fixed in the next beta.