| Anonymous | Login | Signup for a new account | 10-09-09 07:21 CEST |
| Main | My View | View Issues | Change Log | Roadmap | Docs |
| Relationship Graph | [ View Issue ] [ Dependency Graph ] | |||
|
|
||||
|
||||
| Viewing Issue Simple Details | |||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update |
| 0000846 | xmms2d | minor | always | 06-05-28 23:28 | 08-12-17 23:12 |
| Reporter | nano | View Status | public | ||
| Assigned To | |||||
| Priority | normal | Resolution | open | ||
| Status | confirmed | ||||
| Summary | 0000846: cancel result retrieval | ||||
| Description |
The current way: 1. A client requests data from the server, attaches a callback function. 2. The client changed its state and is no longer in need of the result. 3. xmms2d doesn't give a shit and fetches the result and the callback hits. The good way: 1. A client requests data from the server, attaches a callback function. 2. The client changed its state and is no longer in need of the result. 3. The client tells xmms2d that the result is no longer needed. 4: xmms2d removes the result from the query queue and continues with next result. Usecase 1: Pre: A client performs some slow database query, User cries. Post: A client performs some slow database query and provides a cancel button. User pushes the button and smiles. Usecase 2: Pre: A client provides a GtkTreeView that loads only visible data. The User scrolls his 10000+ list of metadata rows at some rate and then stops. Now xmms2d has to process the queue that has built up before the currently "showing" entries can be resolved. User cries. Post: User scrolls, result is available instantaneously, User smiles. |
||||
| Additional Information | |||||
| Mantis 1.1.6[^] Copyright © 2000 - 2008 Mantis Group |