<br>
<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>I was actually thinking the main issue would be things like ff/rewind<br>control, time compression, etc. - things which directly affect the
<br>way the frontend behaves as it's doing the playback and are normally<br>handled by keystrokes sent directly to the frontend app itself. </blockquote><div><br>
the mythwifi plugin <a href="http://studwww.ugent.be/~aveys/mythwifi/">http://studwww.ugent.be/~aveys/mythwifi/</a> sends
commands directly to the frontend via a socket so that can be
handled. I will dig into the protocol tonight to see how the
frontends request media from the backends. If the frontends
request direct objects from the backend then it would not be too
difficult to make a plugin that acts as if it were the real frontend (I
think)<br>
</div><br></div>