That depends. You have some flexibility here.
One of the reasons we have seperate plugins and players for each smart media device we wish to control, is that we can figure out the best way to send a piece of media to its destination, and to send the appropriate commands to the player to be able to handle them.
(you do know you'll need to write a Plugin, as well as your device, right? It's not hard, and you can cut and paste a lot of code from existing plugins to help, but it does need to be done.)
MH Play Media is passed a URL as part of its command, from the controlling Orbiter.
What format this is in, depends on whether the file is local, or some other network resource (e.g. http)
If the file is from a disk that Pluto Storage Devices manages (this is a disk connected either via the core, a media director, or a networked file share over NFS or SMB), then the path is local, like this:
/home/public/data/videos/Some Disk /Superbad.mp4
whereas something like http would be something like:http://somemediaserver.com/blablabla.mp4
Your plugin will receive this, and it will become part of your MediaStream object in your plugin. You can then do whatever you need to do, to get your Player to handle them.
For example, Xine Plugin contains lots of logic to determine:
* Whether we are playing a "local" file
* Whether we are playing a "local" CD or DVD
* Whether we are playing a "remote" DVD in some other drive in the house
* Whether we need to stream this to multiple TVs in the house