On Fri, Nov 14, 2008 at 2:53 PM, Chris Everest <span dir="ltr"><<a href="mailto:chriseverest@gmail.com">chriseverest@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Fri, Nov 14, 2008 at 12:32 PM, Rob Smith <span dir="ltr"><<a href="mailto:kormoc@gmail.com" target="_blank">kormoc@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><br>
</div>Wouldn't a XML-RPC rely on static methods?<br><br></blockquote></div><br></div>Yes. And once you had a good implementation base, I would assume it would be easy to add new methods. Then you could create new interfaces almost anywhere. I am also thinking read+write interfaces.<br>
<br>For instance...<br><br>List Upcoming Recordings<br>Modify a single Recording<br>Create a new Recording<br>Recording priorities.<br>User Jobs/Job Queue</blockquote><div><br>Isn't this somewhat handled by the UPnP/XML infrastructure already in the backend?<br>
<br>Kevin</div></div><br>