Response to /update request, always sends database revision number 2

jasonmc / forked-daapd

A re-write of the firefly media server (mt-daapd). It's released under GPLv2+. Please note that this git repository is a mirror of the official one at git://git.debian.org/~jblache/forked-daapd.git

http://blog.technologeek.org/2009/06/12/217

GNU General Public License v2.0

326 stars 45 forks source link

Response to /update request, always sends database revision number 2 #70

Open stormcock opened 13 years ago

stormcock commented 13 years ago

As the title says, server always returens a database revision number 2 in respone to a /update request - even when the server has updated itself due to changes in the watched music directories. I would expect that this value changes - I use this value in my client to check a cached version of the database against the server version. mt-daapd (Firefly) modifies the revision number whenever changes in the directories are made.

Tim

CraigMarkwardt commented 12 years ago

I submitted a patch to the upstream author to do dynamic updating but it was not accepted. The author was/is making large changes to the database code and apparently didn't want couple the DAAP code and revision code.