<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Jul 17, 2014 at 11:58 AM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 07/17/2014 02:51 PM, Karl Newman wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks, Paul. Mythweb uses DELETE_RECORDING as well (and the recording is successfully deleted), but then follows it with FORGET_RECORDING. Looks like the code just needs to be changed to add the "FORGET" parameter to the DELETE_RECORDING command. So it looks like that should be an easy fix, but I don't see any replacement for FORGET_RECORDING, so the "Forget Old" button in mythweb won't work without deleting the recording. Not ideal.<br>
</blockquote>
<br></div>
FORGET_RECORDING should still work. Delete followed by forget is fine, too (assuming forget works), so MythWeb wouldn't need to change to use the delete command with the forget argument.<br>
<br>
If FORGET_RECORDING is broken, time would be best spent fixing it instead of putting a workaround inside MythWeb (especially if that workaround only works when also deleting a recording).<br>
<br>
Mike<br></blockquote><div><br></div><div>Thanks, Mike. I spoke too soon--I just saw that FORGET_RECORDING is still part of the protocol. Probably mythweb is invoking it incorrectly. I'll see if I can figure out what the backend is expecting and get Mythweb to pass the correct parameters.<br>
<br></div><div>Karl<br></div></div></div></div>