hello mss,
the current version (1.0.5.0) has production status. if there should be bugs, they get fixed and the build number updated.
the next feature planed for twslink
is database support to store orders
and account states. so those familiar
with sql will be able to make researches
on the data.
later we may offer some kind of statistic tool and account monitor tool.
one of the next versions should support multiple tws connections. this will be commercial only.
the lifetime of the twslink project depends on the (monetary) success we have. it is possible that later versions have to be purchased. but i don't think this will be done by monthly fee rather than a single payment.
10000 words to order management.
i am not sure what you mean, but currently there is no order property based on API 9.0 that is not supported by TWSLink.
you can attach orders, place FA orders as well cancel,modify multiple orders by one step.
you do not have to care about connection status. connection is done automatically, orders and cancel requests queued in case of broken connection, same for all other requests (account data, market data, etc.).
so you can use orders in the manner of "fire and forget".
on failure, an extensible log makes it possible to find whats going on.
twslink has no user interface. so you can't really compare it to ninja trader.
however, you should be able to implement your own interface and order input masks. but behind these masksthere is no more work to do than to code:
placeOrder(...)
and thats all.
no tricky use of the native IB API, no plausibility check, no connection checks, no other checks etc. are necessary. all this is done by twslink.
TWSLink is like an abstract layer above the IB API and a subset of IB API functionset.
guaranteed future:
it is not a problem e.g. to shift a strategy written for excel to eSignal or TradeStation or to any other application that supports DLL function call or COM because function calls and principal using remain the same.
additionally it depends only from IBs API. as you know, running various API versions with various TWS versions is no problem. same for TWSLink. further API versions should not make older TWSLink versions incompatible as far IB does not change an request explicitly.
the purpose of twslink is to provide the most important api features, fast and reliable service and accessibility from most application.
in summary: twslink is for saving your time to be able to concentrate on the core of your work: the strategy.
regards,
chinaski