Hi Dukascopy Team,


In my opinion IClient.disconnect() has some deficiencies. Two examples.

First:
1. I start my application using Standalone API, connect to DS, trade something, close application (invoking IClient.disconnect() before) -> OK
2. Right away I start the app again using Standalone API, connect to DS, trade something, close application (invoking IClient.disconnect()) before -> OK
3. Right away I start the app again. This time I cannot connect to Dukascopy (I am being disconnect right after I get a connection). I have to wait 5-10 minutes before I will be able to connect again.

It seems that IClient.disconnect() does not fully release the connection on your (server) side.

Can you please adjust the method so it fully releases connection between my computer and your severs?


Second:
If I call disconnect method during IClient.connect() it seems that connection is interrupted (which was my intention). But, in reality not all connection threads are stopped and login to Dukascopy is still in run. In results sometimes I establish connection even though I called disconnect() method.

Can you please improve disconnect() method so it does stop all login threads when called during logging (connection) process?

Thank you for taking this into account.

Best regards,
kurak

Fixed with JForex-API 3.0