[mythtv] Automatic deletion
Chris Pinkham
cpinkham at bc2va.org
Thu Jul 3 20:07:07 EDT 2003
I have working code right now which implements AutoExpiration of old
files based upon record date. The code is designed to allow easy plugin
of other expiration methods. It runs as a thread on each backend and uses
Myth's internal message passing code so it doesn't have to open any socket
connections. I need to hook up a couple quick screens to allow turning the
'autoexpire' field on/off on the record and recorded tables but then I'll
commit it to CVS. So, give me a few days and then you can just work on
coding other auto-expire methods (like basing it on record rating, etc.)
Once I commit the basic autoexpire core then people can submit patches to
add new expiration methods if they want.
> Having once made a pretty good living as a programmer I went to go add my
> auto-delete feature. I didn't get far before I started to feel dirty.
>
> The backend has code to determine how much free space is available, it also
> has a mechanism to delete recorded files. Great almost everything I need.
> Still it "feels" bad connecting to a socket from the backend, to the backend
> and then creating a string to call the functions and then parsing a string
> to get the results back.
>
> I'm worried about protocol changes, it would be nice if, somewhat like the
> frontend, there was some sort API layer which wrapper the line protocol in
> pretty callable routines. Is this there and I'm just missing it? Maybe
> something like PlaybackSock but abstracting the protocol from the transport
> more?
>
> --
> Anduin Withers
Chris Pinkham
More information about the mythtv-dev
mailing list