I'm using new IQFeed 4.7 approach to launch IQFeed child process with parameters. It's taking several seconds for IQConnect to login and to launch all sockets. If I trying to connect to the socket immediately after process started I can connect to admin socket only. So calling process need to wait for several seconds before connecting. This wait time varies depending of internet channel load and (probably) IQFeed server load.
This is not good approach to wait hardcoded number of seconds because of possibe race. So I created code which tries to connect to Level I socket with 1 second intervals until connected. Then this code holds this socket opened for several seconds to make sure IQFeed will not unload and let the main code to connect to IQFeed sockets. This all code works fine.
But, when main code tries to connect, it receives S,SERVER_DISCONNECTED message and does not work. If I trying to connect to IQFeed again (unload and load again) it repeats S,SERVER_DISCONNECTED message.
What is the correct approach to make sure IQConnect logged in and ready for connection?

On the initial launch, IQConnect only starts the Admin port until the first connection to the servers has been made.

The Stats message that is sent to the Admin socket should tell you when the connection has been established (it will change from saying that IQFeed is "Not Connected" to being "Connected". At that point, it is safe to establish all of your other connections and start making requests.

Hi, Steve.

Thank you very much for your advise. I used it and it working fine.

However I found another problem in the IQConnect 4.7 beta. The problem related to "S,CONNECT" command sent to admin socket. Unfortunately this command prevents IQConnect from connecting even when "S,SET SAVE LOGIN INFO,On" command sent or "-autoconnect" parameter sent through command line. When this command sent to IQConnect it starts in disconnected mode and even does not show login dialog.

Actually I tried to avoid using command-line parameter to pass credentials to IQConenct.exe (this is not safe). So I tried to use the following sequence of commans passed to admin interface:

SendMessageToServer("S,SET SAVE LOGIN INFO,Off");
SendMessageToServer("S,SET AUTOCONNECT,Off");

// Register application
SendMessageToServer(string.Format("S,REGISTER CLIENT APP,{0},{1}",_productName, _productVersion));

// Send credentials to IQConnect
SendMessageToServer(string.Format("S,SET LOGINID,{0}", login));
SendMessageToServer(string.Format("S,SET PASSWORD,{0}", password));

// Force server connection
SendMessageToServer("S,CONNECT");

IQConnect responds with messages that application is registered and credentials are set, but does not login.

Now I have rolled back to passing credentials through command-line parameters and setting "-autoconnect" and "-savelogininfo" parameters. Currently this is only approach which works with IQConnect.

How should I change my code to pass credentials through admin sockects and to make "S,CONNECT" command work correctly?

I am looking into this. If I understand what you are trying to do, it seems like you are doing everything correctly. I'll let you know what I come up with.

This is a bug in the beta. While the Login Dialog is displayed to the user, IQFeed is ignoring the S,CONNECT message sent on the admin socket.

This will be fixed in the next beta build. There will be two changes to the next build in this reguard. First, if IQConnect has not yet recieved a ProductID and Product version, the Login Dialog will not display to the user (it currently displays but with the connect button disabled). Second, if the S,CONNECT command is recieved while the Dialog is displayed to the user, it will Simulate the user clicking the Connect button.

Hi, Steve.

Thank you for reply. I seen the disabled "Connect" button and had all the problems you described. Will wait for the next beta.

Edited by smt52 on Dec 16, 2009 at 11:51 AM

Hi, Steve.

I just downloaded and tested lastest IQFeed 4.7.0.3 beta. "S,CONNECT" command now works, but it works only in one case, wneh:

SendMessageToServer("S,SET SAVE LOGIN INFO,On");
SendMessageToServer("S,SET AUTOCONNECT,On");

sent before the "S,REGISTER CLIENT APP" command. When I send

SendMessageToServer("S,SET SAVE LOGIN INFO,Off");
SendMessageToServer("S,SET AUTOCONNECT,On");

or

SendMessageToServer("S,SET SAVE LOGIN INFO,On");
SendMessageToServer("S,SET AUTOCONNECT,Off");

or

SendMessageToServer("S,SET SAVE LOGIN INFO,Off");
SendMessageToServer("S,SET AUTOCONNECT,Off"); // Most preferred combination

"S,CONNECT" command does nothing. IQConnect shows login dialog, but nothing happening until I click "Connect" button.

It sounds like this is working as intended for you.

The Set Autoconnect command is ignored if the login info is not saved which means that your first scenario (that doesn't work) is the same as the last one.

Essentially, the S,CONNECT command has the same functionality as if the user were to click "Start Feed" from the notification icon's right-click menu. When the user clicks this menu option having not yet logged in, it will cause the login dialog to display.

Anytime the login dialog window is displayed, it checks the save login info and autoconnect flags. If these are both set, it will autoconnect and hide itself (assuming it was successful). If either of them are not set, it will prompt the user to click connect.

We added the functionality that a S,CONNECT command while the dialog is displayed will force a connection attempt (as though the use clicked connect).

As a result, you have a couple options to make this work in the scenarios that you mention. You can either send an additional S,CONNECT command. Or you can set the save info and autoconnect ON, CONNECT, and then set them back off again.

Hi, Steve

Thank you for your kind help. Now it works as expected.

Before I sent "S,CONNECT" once and this happen before dialog showed up.

Now I'm sending "S,CONNECT" every second until it connected and connection works with autoconnect and savelogin both set to off.

I am still not clear on this. In my program, autoconnect is not working as I expected.

When I run my program (and ShellExecute IQConnect.exe), the IQ Connect Login dialog appears. I enter my login and password, and I check the "Save Login And Password/Pin" and "Automatically Connect" check boxes. The program runs fine. Then I exit the program and exit IQ Feed. When I re-run my program, the Login dialog has remembered my kogin and password, but it does not autoconnect, and both check boxes are cleared.

This will surely confuse my users. I can already hear them say "Why does it not autoconnect and why do I have to keep telling it to remember my login?" Is there something else I need to do in my program? It doesn't make sense to me that autoconnect would only work if I am sending the login and password on the command line, which I would rather not do.

Thanks,
Mark

There are issues with the current beta (4.7.0.3) that will be addressed in the next Beta build (4.7.0.4).

Copied from a different thread regarding autoconnect not working as expected:

"
Posted: Dec 22, 2009 10:18 AM Msg. 2 of 4
We have verified the problem and will include a fix in the next Beta build (4.7.0.4) which will be posted after the Holidays.

--------------------------------------------------------------------------------
Lonnie Shumate
Development Manager, IQ Systems
DTN Market ACCESS
"

---

Nathan W. Bartsch - Senior Software Engineer - DTN