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

[stormcock]

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]

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.