Stroller <stroller <at> stellar.eclipse.co.uk> writes:
> I don't understand how you would control either a web-browser, or a > web-server, using DLNA. Agreed. DLNA is new for me too. I'm going to find an integrated receiver with ethernet and drag a laptop into a store and see how is works. There just not much documentation on what each vendor is doing, and asking some penny-poke in the store how it works is useless. Now I've discovered that not lots of (astute) folks have work with this "DLNA" either..... (go figure) > there can be loads of other incompatibilities > when trying to actually stream the music between devices in the home. > But I would reckon that browser compatibility is the least of your > problems. Most likely MicroSoft has infected this space as I cannot find lots of docs about interoperability, testing or certification lists anywhere. Besides that's what vendors (usually) do in my experience..... DLNA is very loose from what I read about it. Oh well, it's now another project and the ethernet port just might not be worth it. I have loads of audio gear already. I'm experimenting and build a sound system for every need, with a method for my kids to be able to use the AV with DVD and terrestrial radio and such. Once last thing. It's nice to have these integrated amps for 'light duty' audio and letting the kids and such use the system. When I power up the big amps (2K watts), I use the 'pre-outs' in the integrated receiver to feed into a mixer. If you make it so you have to use a computer for simple sound then some kids and some folks get flustered..... imho. I think this space is very dynamic as vendors struggle to understand how to let customers have what they want, and still maintain some differential control over their products features...... YEP look here (MicroSuck) is front and center. SO DLNA will SUCK! http://www.dlna.org/about_us/roster/ Just what I feared. I guess vendors are just too stupid to realize all they have to do is put ethernet on the product and document what paramaters to pass over which open standard protocol (RFC) and ports they want to use and Whamo it works...... This is just what I figured it was. Microsoft contaminated crap..... thanks for all the input, James
