Page 3 of 4

Re: 0.2.0 preview release

PostPosted: Tue May 31, 2011 10:30 am
by evgeny.shmakov
frAnton wrote:Thank you for explanation, so if the session dropped then what should the client expect O2GSessionStatusCode.Disconnected, O2GSessionStatusCode.SessionLost, or both?

If the session dropped then client receives:
1) O2GSessionStatusCode.SessionLost;
2) O2GSessionStatusCode.Disconnected.
The new article "Session Status" was added to online help. See more,
http://www.fxcodebase.com/documents/For ... tatus.html
Best regards, Evgeny.

Re: 0.2.0 preview release

PostPosted: Tue May 31, 2011 10:34 pm
by frAnton
evgeny.shmakov wrote:
frAnton wrote:Thank you for explanation, so if the session dropped then what should the client expect O2GSessionStatusCode.Disconnected, O2GSessionStatusCode.SessionLost, or both?

If the session dropped then client receives:
1) O2GSessionStatusCode.SessionLost;
2) O2GSessionStatusCode.Disconnected.
The new article "Session Status" was added to online help. See more,
http://www.fxcodebase.com/documents/For ... tatus.html
Best regards, Evgeny.


Hello Evgeny,

Thank you for the chart, good job.
I have a question though with regards to the session status. Please correct me if I am wrong, but according to the chart when the connection to the Price Server's lost the Client would receive the ‘SessionLost' and ‘Disconnected’ status only if the MaxReconnectAttempt was reached.
So the Client might not even be informed at all that the trading settings has been updated on the server, is that right?

Thanks,
Anton.

Re: 0.2.0 preview release

PostPosted: Wed Jun 01, 2011 11:37 am
by Nikolay.Gekht
I see you problem. Just check the trading properties every time when connected status appears.

BTW, in case the trading settings are changed, the command to forced reconnect will be received from the server. I think Eugene can explain better what happened in this case.

Re: 0.2.0 preview release

PostPosted: Wed Jun 01, 2011 1:46 pm
by frAnton
Nikolay.Gekht wrote:BTW, in case the trading settings are changed, the command to forced reconnect will be received from the server. I think Eugene can explain better what happened in this case.


Thank you for your answer,
That is pretty much close to what I asked in terms of introducing TraddingSettingsUpdate event.
It would be really helpful as the Client would know in this case that it has to restart itself in order to get new settings from the server etc.

thanks,
Anton.

Re: 0.2.0 preview release

PostPosted: Thu Jun 02, 2011 7:34 am
by evgeny.shmakov
Usually trading settings are changed during server maintenance. The
session status is "Disconnected" during maintenance. After maintenance
is completed, you can perform login and get the updated trading
settings.

Sometimes (very rarely), the trading settings are changed when you are
logged in. Changing of some trading settings can require logout. In this case
the connection status will be changed to "SesseionLost" and then to "Disconnected".
So you have to perform login. In this case you can also get the updated trading
settings after login.

Note that, in case the trading settings have been changed during
reconnecting, you should update the trading settings once the
"Connected" status appears.
However, in the current version API doesn't provide the updated
trading settings in this case. The issue will be fixed in the nearest
June release.

Note that monitoring of the connection status is not enough to be
informed that the trading settings have been updated because the
settings can be changed without restarting the server. In this case
the connection status won't be changed.

We'll add the TraddingSettingsUpdate events in one of the next
version of API for correct processing of the trading settings.

Re: 0.2.0 preview release

PostPosted: Thu Jun 02, 2011 11:41 am
by frAnton
Thank you for a such detailed explanation. Looking forward to get a new version of FxConnect API.

thanks,
Anton.

Re: 0.2.0 preview release

PostPosted: Mon Jun 20, 2011 11:23 pm
by frAnton
Are you guys expecting to release a new version of FxConnect API any time soon?

Thanks,
Anton.

Re: 0.2.0 preview release

PostPosted: Tue Jun 21, 2011 5:31 am
by sunshine
Hi Anton,

The next beta version is expected in the beginning of the next week.

0 2 0 preview release

PostPosted: Mon Dec 26, 2011 8:41 pm
by Anariamic
I havent tried preview 2 with this new update, does it make it a stable release to be a daily driver? I had it on my mac air before this new update and it was really buggy so I had to take it off.

Thanks, Nexttonomy

Re: 0.2.0 preview release

PostPosted: Tue Dec 27, 2011 12:06 am
by sunshine
Hi Anariamic,

The ForexConnect API has been officially released. It has the version 1.0.1.
Besides the new beta version with the table manager (1.1.1) is available.

To download the API, please visit the Download page in FXCodeBase wiki.

To learn about all API releases, please visit the page Release Notes.

If you have any questions, please do no hesitate to post them.