| API Support » Auto Reconnect Feb 20, 2014 @ 08:32 PM (Total replies: 9) | |||||
|
Hi OEC, Do you have a solution or workaround for this problem? Or please confirm that this exception can be ignored without bad consequences. Thanks Ruslan Enikeev |
|||||
| API Support » Auto Reconnect Feb 08, 2014 @ 10:00 AM (Total replies: 9) | |||||
|
Quote: I'm finding that after reconnecting I must resubscribe to ticks for each contract so that ticks are received again in the OnTicksReceived event. Does that make sense? And then sometimes after reconnecting I'm getting an error that I've subscribed to too many contracts -- implying that the subscriptions weren't really "lost." Do I have to unsubscribe then resubscribe after reconnecting? I'm confused. Help? I experience the same problem. If disconnect-connect happens quickly seems that it does not lose contracts' subscription and re-subscribing causes "subscribed to too many contracts". If the delay is bigger it works smoothly. It can be easily reproduced if you run the app, unplug network to cause disconnect and plug it again. OEC, is there a workaround to understand whether I need resubscribe? Ruslan Enikeev |
|||||
| API Support » OnPriceTick is fired many times with the same data Jan 19, 2014 @ 09:27 PM (Total replies: 2) | |||||
|
Hi Victor, Yes, I am. I checked that. Ruslan Enikeev |
|||||
| API Support » OnPriceTick is fired many times with the same data Jan 19, 2014 @ 09:05 PM (Total replies: 2) | |||||
|
Hi OEC, I found strange thing: event OnPriceTick is suppose to be fired only when Bid/Ask or Last Trade changed but actually it fires many times with exactly same input data. Please have a look http://myscreenshot.info/i/0003/771071390183260525286605060340.png last_Price is the previous input, Price is the current one. As you can see they are absolutely identical. It happens more than two times sequentially. Is it a bug? Thanks, Ruslan Ruslan Enikeev |
|||||