On November 1, 2007 12:24:22 Thomas Perl wrote:
> Hello, Chris!
>
> On Wed, 2007-10-31 at 19:39 +0100, Chris McCabe wrote:
> > Sorry to comment on my own message, but now that I think of it a bit
> > more, why not just use the entire URL of the actual podcast, instead
> > of the feed. For example, the podcast downloaded from:
> > http://www.hbo.com/video/podcasts/billmaher/637314_dl.mp3
> >
> > would be stored at the following location in the filesystem:
> > www.hbo.com/video/podcasts/billmaher/637314_dl.mp3
> >
> > Every podcast must have a unique URL, so you know it's always unique,
> > and always exists.
>
> Yes, that's a nice idea, but I have some uncertainties her:
>
> * What about URLs like www.example.com/podcasts/download.php?id=5
> * When a feed stores its episodes on different servers, these
> will be spread out in the "download directory", and therefore
> one cannot easily delete a whole channel in the filesystem with
> a single
>
> Other than that, I like your idea, but I don't know if the other
> requesters of this feature have an easier time searching through a
> (probably) deep directory structure instead of a "flat" channel/episode
> structure.
>
> The implementation would not be too difficult, but "old" episodes would
> have to be rewritten/renamed.
>
> What do the others think of this proposal?
>
> Thomas
Hello,
I've been looking through the suggestions and an idea that didn't come up was
a simple enumeration at the beginning or ending of directory and file names.
For example it could look something like this:
~/{download dir}/{number}-{<title> (cut off if too long)}/
{number}-{show title (also cut off if too long) or original filename}.ext
~/gpodder-downloads/03-This_Week_in_Tech/19-Some_random_show.mp3
The numbers could be assigned randomly (in that case a bigger number would be
needed) or the numbers could simply be counters that gpodder keeps track of.
I think this would be nicer than having to descend through many oddly named
directories to find a show you're looking for.
Just my $0.02,
nick
_______________________________________________
gpodder-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/gpodder-devel
