ConnectionEstablished event

[Luis Reis]

The ConnectionEstablished event is being triggered twice using TCP although in HTTP it just triggers once as expected. My code is exactly the when I use either one of the dlls in which the only change made was changing Settings.DisableHttpPolling=false to true. I'm 100% sure that the .Connected() is only called once and the only thing that the ConnectionEstablished procedure does is to print a string. Is this the intended behaviour or is it a bug?

[Pang WU]

It should be a bug, did you try out the latest code in the git repo?

[Pang WU]

Hi there,

I tried this out in example client, it only triggered once.
I think the reason you have this problem might be two-fold: 1) You have a very old MSNPSharp lib. 2) Your code have problem.

Please check out the latest code from our git repo and test the example client, if that client doen't have this behavior, you may want to check your code then.

On Sunday, 9 September 2012 16:26:43 UTC-7, Luis Reis wrote:

[Luis Reis]

Hi there,

 

Just tried with latest from GIT, I was using 5.04 because didn't think the change was relevant but anyway the problem persists. I've rebuilded the dlls again with both HTTP and TCP polling (before I had builded myself TCP only and HTTP was downloaded) to test if it was because I was building with VS 2012 but it seems that's not the case. Did you test with any option I don't know about that uses TCP instead of HTTP using the same dll or did you build a new dll with Settings.DisableHttpPolling=true?

[Luis Reis]

Just tried the example client and it still happens. I added a messagebox to the connectionestablished, when using http 1 messagebox pops and when using tcp 2 messagebox pop.

[Luis Reis]

By the way forget about the noob chat about compiling the dll with Settings.DisableHttpPolling=true. I thought I had to modify the MSNPSharp source and compile different dlls but I just found out that I can also use it in my code for the same effect :)

[Pang Wu]

Hi Luis,

Can you share me the code of  the messagebox?

[Pang Wu]

I just uncomment // Settings.DisableHttpPolling = true; in example client's ClientForm() constructor.

[Pang Wu]

btw, I am testing it with Mono on a Mac, but I don't think this will cause the difference.

[Luis Reis]

I tested it by adding      MessageBox.Show("string");     to NameserverProcessor_ConnectionEstablished in DotMSNClient.cs. When you use TCP don't you see 2 boxes popping up?

[Pang WU]

If your code looks like following:

private void NameserverProcessor_ConnectionEstablished(object sender, EventArgs e){

MessageBox.Show("String");

            if (InvokeRequired)

            {

                BeginInvoke(new EventHandler(NameserverProcessor_ConnectionEstablished), sender, e);

                return;

            }

            SetStatus("Connected to server");

        }

You are for sure getting two message boxes because the BeginInvoke(new EventHandler(NameserverProcessor_ConnectionEstablished), sender, e); call this method again. For TCP the data was delivered in a thread that differ from the UI thread, that's why we need that line. And this is not a bug, please read more about C# UI sync.

[Luis Reis]

void ConnectionEstablished(Object sender, EventArgs e)
{
   f.Invoke((MethodInvoker)delegate { f.print("Connection established"); });
}

 

That's the code I've been using and printing "Connection established" twice for TCP and once for HTTP.

 

If you say it's because of the     BeginInvoke(new EventHandler(NameserverProcessor_ConnectionEstablished), sender, e);     try deleting the whole "If" that has the     BeginInvoke(new EventHandler(NameserverProcessor_ConnectionEstablished), sender, e);     including everything inside the "if" and add     MessageBox.Show("string");     in the procedure.

When the first box appears you click ok and then you will see another box popping up.

 

Btw besides the ISP blocking problem mentioned somewhere and the fact that the account stays online after internet disconnection 10 secs for HTTP and almost 2 mins for TCP, what's the difference between TCP and HTTP? Any behaviour change or connection speed or messaging latency?

[Pang WU]

Hi,

I repeated your issue. The event was triggered twice because TCP connection was redirected by the server. This is the normal behavior of MSN clinet-server login interaction.