[jitsi-issues] [JIRA] Closed: (JITSI-789) Google Talk connect is slow

ibauersachs (JIRA) jira-no-reply at java.net
Mon Jan 14 13:51:53 CET 2013

     [ http://java.net/jira/browse/JITSI-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ibauersachs closed JITSI-789.

         Assignee:     (was: jitsi-issues)
    Fix Version/s:     (was: 2.0)
       Resolution: Cannot Reproduce

Speedy now, please reopen if its still slow for you.

> Google Talk connect is slow
> ---------------------------
>                 Key: JITSI-789
>                 URL: http://java.net/jira/browse/JITSI-789
>             Project: jitsi
>          Issue Type: Improvement
>          Components: development
>    Affects Versions: future
>         Environment: Operating System: All
> Platform: All
>            Reporter: lubomir_m
> I've been seeing it for a long time: connecting a Google Talk account in SIP
> Communicator (regardless of whether it's newly created or an existing one which
> was manually disconnected and then reconnected) takes noticeably longer than it
> takes in Empathy, Pidgin. It takes more than 10 seconds for SIP Communicator to
> get connected and display the online contacts while Empathy succeeds to achieve
> the same result in about 2-3 seconds. I even tested with meebo.com and it
> managed in 5 seconds.
> I vaguely remember there was some SSL/encryption-related initialization in the
> MSN protocol implementation which I was very slow and Damencho said (well, this
> is a recollection of mine so it may or may not have ever happened) it was also
> executed in for the Jabber protocol implementation.
> I'd very much appreciate it if connecting a Google Talk account and displaying
> its online contacts can be sped up. I've seen this issue many times, yet I seem
> to pretty much always be thinking when my Google Talk account is connecting that
> I haven't started the connection procedure. (I know the fact that there is no
> visual feedback during the connecting phase of an account contributes to my
> perplexing but this issue is about the additional slowdown.)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://java.net/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the issues mailing list