How about a proxy model? As I understand it (and I haven't gone so far as to capture packets on the wire), SqueezeNetwork (SN) is essentially a case of the SB player connecting to a SlimServer (SS) host that's run by Slim Devices on the public Internet. Once "on" SqueezeNetwork, a player sends all IR events to the SN server, which controls it. This is why the SS does not include in its list of current players any local SB that's connected to SN.
I'd like to see SS implement an (optional? configurable?) proxy model. SB players would access SN *through* their normal SS hosts (if the normal SS host is available). The SS host would receive IR events from the SB, pass them to SN, and pass the SN output back to the SB. This would allow for a few benefits: - IR "filter" plugins Plugins on the local SS host could intercept IR codes to take action and possibly modify, remove, or add IR codes before they're sent to SN. - local SS oversight The local SS process would retain direct control over the SB. If a home automation system wanted to start playing a certain playlist on a given player, it could end the player's SN session and resume "normal" SS/SB behavior. If a customer wanted some volume or activity curfews, those could be applied to SN activity as well. Ideally the SS/SN connection would have some fuctionality like the CLI "listen" command, and ideally the SS host would make those events visible through its CLI. Perhaps there would need to be a namespace/prefix convention for that information, e.g. prepend "SqueezeNetwork::" to the info that SS passes along to its CLI clients about SN activity for a given player. For my most recent plugin -- one that uses X10 to control the AC power to my receiver/amp in conjunction with SB power state changes -- it means my plugin could see when a SB connected to SN was powered off. Currently, my plugin only sees power state changes when the SB is not on SN, so my amp is only powered down when I turn off my SB if I'm *not* using SN. I imagine there might be some concern about DRM with a proxy model, especially if the music "data" flowed through the SS proxy software. Proxy mode would likely facilitate copying data streams sent by SN to SB players. I don't know if that's much of a concern though, considering that the Slim protocol is documented and anyone who's got an SB can already read the packets as they cross their home networks. So I hope those fears would not dissuade Slim Devices from including a SS/SN proxy option. -Peter -- peterw ------------------------------------------------------------------------ peterw's Profile: http://forums.slimdevices.com/member.php?userid=2107 View this thread: http://forums.slimdevices.com/showthread.php?t=23707 _______________________________________________ squeezenetwork mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/squeezenetwork
