do we need to wait for initialFillSize again?
should we do that?
what if the resource has a different mimetype than the item??
who will sync mimetype that is part of the protocl info and that is lying in the resources with the information that is in the resource tags?
currently resource is misused for album art
resource options must be read from configuration files
move this down into the "for" loop and create different urls for each resource once the io handlers are ready
we could figure out the content length...
turned out that we are not always allowed to add this header, since chunked encoding may be active and we do not know that here
description should be taken from the dictionary
change the text string to element, parsing should be done outside
is there a default setting? autoscan? import settings?
is there a default setting? autoscan? import settings?
1.6.1