I received an email today with questions that I have been asked many times, so I thought I’d post the questions and answers here.
- If you stop maintaining your wrapper to the latest versions and the IB API changes to newer versions, how long will your existing C# API wrapper keep working?
Ib goes to great lengths to maintain backwards compatibility with old apis. If you look at their api code, it is clearly version controlled by the method, and I wouldn’t be surprised if code from many years ago still works.
As an example, I have been running an API app I wrote in Jan / Feb of 2008 every day since without updating the api once and have had no problems.
- If you stop maintaining your wrapper to the latest versions, would you possibly update it for a small fee? (I am not rich, just trying my hand to get rich!) I would hate to lose all the effort into coding this ATS.
Always a possibility, but it is my intent to keep updating it for free. I’ve become somewhat less reactive to Ib version updates because each update adds relatively obscure features, and since compatibility is always maintained, it is not super urgent. That being said, I will get myself caught up here shortly, and continue to update to the latest version.
- Has your wrapper matured over time and currently working well? No inherent hard to debug problems? (Sorry for my asking but my Delphi friend has many of these!) I noticed your excellent forum for help.
Good question, it certainly has matured. Occasionally some parsing bugs have been pointed out, specifically with my use of decimals, but I address those quickly with updates to subversion, and changes get rolled into the next release.
Let me know if you have any other general questions and I will create an FAQ page.
