Feature #242
Entry Command Queue
| Status: | Closed | Start: | 11/29/2009 | |
| Priority: | High | Due date: | ||
| Assigned to: |  Mirco Bauer |
% Done: | 100% |
|
| Category: | Frontend GNOME | |||
| Target version: | 0.7 | |||
| Complexity: | High |
|||
| Votes: | 0 |
Description
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.
Related issues
| related to Smuxi - Bug #332 | Messages may be send to the wrong network | Closed | 02/02/2010 | ||
| blocks Smuxi - Feature #24 | Lag indicator (frontend <-> smuxi-server) | New |
Associated revisions
Revision d2533d47ad65d591afa2ec93faf9a6e7f38d98d3
Process commands in a queue (closes: #242)
The Entry field now uses the CommandManager class with is processing the
entered commands in a queue using a thread.
History
Updated by Mirco Bauer 5463 days ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset d2533d47ad65d591afa2ec93faf9a6e7f38d98d3.