> What if someone implemented a MAME OSD layer that forwarded textures and audio > segments over a network connection to a remote peer that did nothing except display > those textures/audio and then supplied input back over the network to be fed back > into MAME?
I'd say that's a seriously inefficient way to do what ClientServerMAME (or OnLive, for that matter) does.
> Does that violate the MAME license? MAME itself is running in a binary > that is not being distributed, but the runtime results of the MAME executable - audio > and video, and user input going back the other way - are being distributed over the > network. Does that count as a license violation?
It sounds as if you intend to try and violate MAMEdev's intent in that specific way, in sort of a "no, Mr. Bond, I expect you to die" manner. I'm sure you're not actually planning to do that, so please explain your *real* use case.
|