From what I have observed, iTunes does not use updates as a keep alive mechanism. It can leave an update request pending for hours and only replies when the database changes.
This mechanism seems to have been introduced in forked-daapd to prevent bugs related to session expiration after 30 minutes. I guess some previous version of iTunes accepted the same revision number and subsequently requested the database again, which would reset the session expiration timer. I do not know how iTunes handles session expiration. I have seen that replying with a mupd and a musr of 0 causes iTunes to properly close the connection (i.e., request /logout). It might be more appropriate to let the session expire gracefully and notify iTunes than to hijack updates. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
