Bug 119109

Summary: mark not acknowledged lines
Product: [Applications] konversation Reporter: Emil Obermayr <nobs>
Component: generalAssignee: Konversation Developers <konversation-devel>
Status: RESOLVED NOT A BUG    
Severity: wishlist    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Emil Obermayr 2005-12-28 12:00:26 UTC 
Version:           0.19 (using KDE KDE 3.4.0)
Installed from:    SuSE RPMs

Sometimes it takes a long time till entered text is sent to the server and acknowledged by it.

I would like to have those lines which no one else has seen marked. Maybe like this:

not even sent to the server: low contrast; dark gray on light gray

sent to the server but not acknowledged: medium contrast; dark gray on white

I am not sure how this acknowledge could work. #-lines are sent back to the sender, I think. But with queries im not so sure; maybe a TCP-feature could be used?
Comment 1 Eike Hein 2005-12-28 15:16:22 UTC 
Addendum: I've previously thought about visualizing how much of a line got through and what got omitted or cut off by the server in case of overly long lines.
Comment 2 Thiago Macieira 2005-12-28 15:26:57 UTC 
This is not possible, from what I know of Konversation. Everything is sent immediately, so what may happen is that it gets stuck in the network layer.

To get stuck on KDE's socket layer, you must have sent at least 16kB of text (it's generally way more) to the IRC server and it did not respond. So, unless you're flooding the server at a high rate, our frameworks won't even know the server did not get anything yet.

And no, there's no way to get the kernel to tell us in a portable manner it hasn't managed to send stuff to the server yet.

The way I see it, this bug is a WONTFIX (since IMPOSSIBLE isn't an option). I'll leave this open for Konversation developers in case I'm wrong about it sending stuff immediately.
Comment 3 Eike Hein 2005-12-28 15:52:24 UTC 
@thiago: Well, the server returns the lines it gets to us too, so the questions is whether we can come up with a reliable heuristic that can make the connection between what we send and receive.
Comment 4 Thiago Macieira 2005-12-28 15:58:11 UTC 
The server doesn't echo back what we send to it.

Unless you're proposing to send a PING after every single PRIVMSG command sent, in order to determine whether it was received, I don't think we can do this.

Besides, it may also give a false sense of security. Even if the server got the PRIVMSG and processed it, it *still* doesn't mean anyone has seen it. There are more network delays involved in sending it to other servers and other users. Don't tell me you've never been on a lagged IRC server.
Comment 5 argonel 2005-12-28 18:55:38 UTC 
sorry, this is impossible without support from the irc server. the connection is not full duplex and no ack exists. even if the message is received by the server, there is no guarantee that the server forwarded it to any clients at all. such is the nature of irc.

we can however do more about overly long lines, but that is not the substance of this bug report.