[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 139418] jabber: typing notification sent twice
From:       Jan Ritzerfeld <kde () bugs ! jan ! ritzerfeld ! net>
Date:       2006-12-31 22:44:46
Message-ID: 20061231224446.10494.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=139418         
kde bugs jan ritzerfeld net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
      everconfirmed|0                           |1



------- Additional Comments From kde bugs jan ritzerfeld net  2006-12-31 23:44 \
------- Many thanks for your debug output. You were completely right. Kopete is \
indeed sending out too many jabber composing events when you are typing for a \
sufficiently long time. "Too many" because section "5.3 Repetition" of XEP-0085 \
states that "Even if the user types continuously for a long time (e.g., while \
composing a lengthy reply), the client MUST NOT send more than one standalone \
<composing/> notification in a row."

I've made a patch that, among other things, has the drawback of changing the public \
API of JabberChatSession in order to store the last sent chat state event. :-/ For \
this reason, I did not commited it ... At least, I'll try to fix the other things \
first.


[prev in list] [next in list] [prev in thread] [next in thread]