[Psi-Devel] [haas at debian.org: Bug#450736: psi: Sending GPG-encrypted messages is delayed by 4 seconds]

[Andreas Ntaflos]

On Sunday 11 November 2007 19:20:40 Stefan wrote:
> As the user doesn't tell which server he uses (or if he tried it with
> another) and how long his gpg key is, I can't say that my suggestion is
> right.
>
> One point can be that he uses a server which has a bandwidth limit for
> the messages. If he uses a server that has a limit of 1 kb per second
> (which e.g. swissjabber has) and his key is 4 kb long then you can
> calculate, where the 4 seconds do come from :)

How would that make Psi itself unresponsive? As Justin mentioned earlier [1] 
Psi uses QProcess to launch gpg. That should be asynchronous, and no matter 
what bandwidth limitations the server imposes, Psi should not block 
completely. At least that's how I understood it.

I also run my own ejabberd server at pseudoterminal.org and definitely have 
not configured any bandwidth limitations. But using the echo module 
(mod_echo) to send an encrypted (chat) message results in the same 2 to 4 
second hang of Psi. The same is true for sending a message to a contact at 
another server that I know doesn't impose bandwith limits. And, last but not 
least, Psi 0.10 didn't behave that way, ever.

Unfortunately I don't know how to debug this further.

Andreas

[1] 
http://lists.affinix.com/pipermail/psi-devel-affinix.com/2007-October/007349.html
-- 
Andreas "daff" Ntaflos 
Vienna, Austria 

GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC  7E65 397C E2A8 090C A9B4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.affinix.com/pipermail/psi-devel-affinix.com/attachments/20071111/45030219/attachment.pgp