Bug 126577 - Lag in message transmission
Summary: Lag in message transmission
Status: RESOLVED FIXED
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 0.19
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-01 19:30 UTC by Florent Bruneau
Modified: 2006-07-03 11:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florent Bruneau 2006-05-01 19:30:10 UTC
Version:           0.19 (using KDE KDE 3.5.2)
Installed from:    Gentoo Packages
Compiler:          gcc 4.1 
OS:                Linux

When I write a message, there is a delay between the end of message edition and network transmission. This delay is at least 2 seconds, and sometimes it reaches more than 20 seconds.

This is very annoying when in intense conversations...

I have this delay for all messages even if there is no problem of flooding (I checked with tcpdump to be sure it was not a problem from the server).
Comment 1 Florent Bruneau 2006-05-01 21:27:01 UTC
It seems that it is a consequence of the exponential growth of the 'timerInterval'. I made the following patch. The problem of this patch is that it may remove the flooding protection.

diff -ur konversation-0.19/konversation/src/server.cpp konversation-0.19.new/konversation/src/server.cpp
--- konversation-0.19/konversation/src/server.cpp   2006-01-30 09:43:46.000000000 +0100
+++ konversation-0.19.new/konversation/src/server.cpp   2006-05-01 21:15:53.000000000 +0200
@@ -1212,7 +1212,7 @@
     {
         outputBuffer.append(buffer);

-        timerInterval*=2;
+//        timerInterval*=2;
     }
 }

@@ -1223,7 +1223,7 @@
     {
         outputBuffer.insert(outputBuffer.at(pos),buffer);

-        timerInterval*=2;
+//        timerInterval*=2;
     }
     else
     {
Comment 2 Peter Simonsson 2006-07-03 11:13:32 UTC
I fix it a bit differently in svn trunk, will be in 0.20. Please reopen if you still can reproduce it. Thanks for you report