Forum: C2 Software Development
| |
| Subject: | Questions on using autotrade api |
| Posted by: | Lawrence Lewis |
 |
| |
|
| When: | 9/28/07 (13:52) | |
|
|
|
|
| | 1. When acknowledging a signal or cancellation, should I wait "pollinterval: milliseconds bewteen acknowledgements?
2. When acknowledging signals (using cmd=confirmsig), the first 2 signals work fine, all the other attempts at confirming the rest of the signals result in an http timeout. I do this in a tight loop (c#) with timeout set at 7 seconds. Any suggestions? |
|
| | |
|
| |
|
| |
|
|
|
| | In response to post by Lawrence Lewis of 9/28/07 (13:52) 1. When acknowledging a signal or cancellation, should I wait "pollinterval: milliseconds bewteen acknowledgements?
...
See entire
Let me answer your question #1, then ask for clarification on question #2.
#1) When doing any sort of acknowledging in the C2ATI (AutoTrading API), then you do not need to respect the pollinterval. The pollinterval should only be used between polling for new signals (i.e. it is the length of time between cmd=latestsigs requests). All other activity can happen at your program's convenience; that is, you can feel free to acknowledge things right away.
#2) Can you post or send me via email a log of the transcript between server and client? If you have any password info in the log, please be sure to clean it before posting here.
|
|
| | |
|
| |
|
| |
| Subject: | Questions on using autotrade api |
| Posted by: | Lawrence Lewis |
|
| |
|
| When: | 10/01/07 (19:44) | |
|
|
|
|
| | In response to post by Matthew Klein of 9/28/07 (14:01) Let me answer your question #1, then ask for clarification on question #2.
#1) When doing any sort of acknowledging in the C2ATI (AutoTrading API), then you do not need to respect the pollinterval. The pollinterval should only be used between polling for new signals (i.e. it is the length of time between cmd=latestsigs requests). All other activity can happen at your program's convenience; that is, you can feel free to acknowledge things right away....
See entire
Thanks for getting back to me so quickly.
Of course, this morning, it works fine. I'll run with fiddler for a few days and let you know if I have any problems. |
|
| | |
|
| |
|
|
|
|
What is the C2 Score?
Collective2 rates every trading advisor in its database and assigns a score between 100 and 1000.
In general, a rating above 500 is good. A rating above 700 is excellent.
Collective2 Ratings are recalculated daily based on the entire performance history in our database. The exact formula we use is proprietary, but there are several key variables that go into the Collective2 Rating. One of the most important factors is the length of time we have been able to observe the performance of the trader. Another key factor is the amount by which the trader over-performs or under-performs the S&P 500 index. Finally, the choppiness of the trader's results is taken into account. Certainly a more consistent trader will be rated more highly than a trader with erratic results.
