Comment 2 for bug 457526

We had to modify Tasque to enforce RTM's rule of "one request per second", or else RTM was sending corrupt responses. I believe both initial startup and adding tasks consists of multiple requests, which would explain the problem (multiple requests => multiple seconds).

Although reducing the number of requests would be a good thing, the real solution is to implement caching (aka offline support), so that when you start Tasque is loads a cache of what was there last time, and does the sync with RTM in the background so the user has a faster experience. Same with adding/editing...it would happen instantly in the UI, and the sync to RTM would occur in the background.

Patches welcome, as Tasque is not in very active development right now.