Years back Sonos introduced “their own” Windows Music Library Sharing (disambiguation: the SonosLibraryService) as part of the Windows Desktop client. I believe this was rolled out shortly after S2 arrived, at the time when many of us were highlighting the awkward reliance on SMBv1. SonosLibraryService creates a Sonos-only HTTP (or is it HTTPS?) share, tho’ don’t quote me on that. In any case, this solution works easy-peasy.
So amongst the breaking “thou shall not use SMBv1 or HTTP!” brouhaha, the QUESTION is “IN or OUT” for SonosLibraryService on a forward going basis?
And if the answer is “IN”—which would be copacetic from my perspective—how will SonosLibraryService be installed/updated given that the Windows Desktop Client is being taken out and shot?
Best answer by controlav
View original
