search

ncoronado / tracshell

Automatically exported from code.google.com/p/tracshell
1 stars 0 forks source link

cache data #20

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Describe the enhancement in detail.

Cache data locally per session

What files will be affected?

trac.py

How will the enhancement benefit the project?

Will reduce the number of XML-RPC calls to the server and make the program
more responsive overall.

What side-effects (if any) will the enhancement create?

There might be a need to refresh/clear the cache periodically to see
changes made to a ticket on the server.

Original issue reported on code.google.com by j.kennet...@gmail.com on 3 Mar 2009 at 5:27

GoogleCodeExporter commented 8 years ago 
had a couple use cases which would have made this feature extremely useful

Original comment by j.kennet...@gmail.com on 11 Mar 2009 at 3:53

GoogleCodeExporter commented 8 years ago 
Can you be more specific about the use cases? The traffic going on in a xmlrpc 
connection with Trac is pretty 
lightweight IMO and not worth caching (especially since the tickets may change 
between two requests).

I'm not sure it's worth it.

Original comment by hsoft@hardcoded.net on 6 Apr 2009 at 3:34

GoogleCodeExporter commented 8 years ago 
it's not an issue of bandwidth but of latency.

the data doesn't always change between requests and on a bad connection, 
waiting for
each call slows down the user experience and cuts into productivity (which is 
the
whole point of this tool)

Original comment by j.kennet...@gmail.com on 9 Apr 2009 at 7:25

GoogleCodeExporter commented 8 years ago 
What would you suggest, a 5 minutes timeout or something? If type "v 42" and 
that the ticket 42 has been 
updated 3 minutes ago, I probably want to have the latest changes. There's no 
way for TracShell to know if the 
ticket has been changed without hitting the server.

Of course the data doesn't always change between requests, but there is always 
a chance that it changed.

Original comment by hsoft@hardcoded.net on 9 Apr 2009 at 7:53

GoogleCodeExporter commented 8 years ago 
will switch to low-priority then. this might take some prototyping to validate 
the
use-case.

Original comment by j.kennet...@gmail.com on 10 Apr 2009 at 4:52

GoogleCodeExporter commented 8 years ago

Original comment by j.kennet...@gmail.com on 10 Apr 2009 at 4:53