I generally agree - I dont see any harm in adding config options to manage the cache as well as dbus methods to manage it I can see worst case scenarios where lots of different volumes are added and wastefully indexed which bloat up our database. Having a means to manage this would be good jamie On Fri, 2009-06-12 at 16:37 +0300, Ivan Frade wrote:
Hi Brandon,
I haven't check the code in the patch, just read the document. Why do
we need to add this logic? I think that the common use cases are
covered with our "limited amount of volumes" cache.
In the case we needed to modify the volumes table size, it could be
implemented also as a simple configuration option. Besides, I dont
know if it is a good idea to add new methods in the API for the 0.6.x
series, when the 0.7.x will be a completely new API.
Regards, and thanks for you interest and the work done!
Ivan
On Wed, Jun 10, 2009 at 7:34 PM, Christensen, Brandon
<Brandon Christensen windriver com> wrote:
Please see the attached patch for some enhancements to
removable media support. The patch applies to tracker-0.6.94.
I have also attached a PDF with more detail of the changes
that are included in the patch.
Thanks,
Brandon
_______________________________________________
tracker-list mailing list
tracker-list gnome org
http://mail.gnome.org/mailman/listinfo/tracker-list
_______________________________________________
tracker-list mailing list
tracker-list gnome org
http://mail.gnome.org/mailman/listinfo/tracker-list
Attachment:
wifi-radar.desktop
Description: application/desktop