Entry Command Queue
|Assigned to:||Mirco Bauer||% Done:||
The entry is currently doing calls to the (remote) engine which waits for the command to be processed. When using Smuxi in high latency networks (say UMTS or a busy DSL line) it will block the output and also stops you from writing more messages. This is annoying for the user experience.
A solution to this problem would be to use a command queue rather than sending each command directly to the engine and process the queue in a background thread. The frontend could also show a progress bar and even a lag-indicator for the queued commands.