>It's not as strange as it first seems to be: this method allows us not >only to provide services which we couldn't make otherwise available in the >open source SC (such as Pandora, Rhapsody etc.). But it allows to easily >fix/update services without the need for the user to update his >installation. And as SQN does the job of managing these directories >anyway, we can reduce complexity in SC, reducing memory consumption etc. > That's all very well, but when SN is down, nothing works! If a change is made to support a service in SN, then everyone immediately sees that change, which is good if it works, but if it doesn't, everyone is stuck. Will the SN changes be compatible with all versions of SC, or would it force users to upgrade SC to be compatible with SN services?
For something like Live365, which I never had a problem with before, I cannot now play any radio streams, currently because www.squeezenetwork.com doesn't seem to be available. There is still a Live365 plugin, which now connects to SN to get radio stations. If it can't see SN to get the data, it should use a locally cached version of at least the users preset channels. _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
