FLEB
Jan 11th, 2005, 08:17 AM
I've got a few technical questions, so I'll air them all in one thread:
1.) I've got this idea in mind for dynamic content in a podcast, but part of the plan involves making the MP3 link an HTTP Redirect (via the status code). The question: Do RSS/Podcast clients generally support HTTP redirects? What type (301, 302, or 307) of redirect is best?
I'd simply like to generate the dynamic file once, as needed, then redirect to the generated file in a temp-directory, so Apache can handle issues like partial-content serving (HTTP streaming) and load.
2.) Also, does anyone know a good way of concatenating MP3s and slapping an ID3 on them, on-server? I'm working off a Linux server, and although most of the app would be made in PHP, I'm not completely averse to the compilation-performance hit I'd take by calling-out to a Perl script.
I'd rather not use something that involves compiling, as it's a host's server and I don't have access to gcc. I've heard both "yea" and "nay" on just concatenating the actual MP3 files together.
1.) I've got this idea in mind for dynamic content in a podcast, but part of the plan involves making the MP3 link an HTTP Redirect (via the status code). The question: Do RSS/Podcast clients generally support HTTP redirects? What type (301, 302, or 307) of redirect is best?
I'd simply like to generate the dynamic file once, as needed, then redirect to the generated file in a temp-directory, so Apache can handle issues like partial-content serving (HTTP streaming) and load.
2.) Also, does anyone know a good way of concatenating MP3s and slapping an ID3 on them, on-server? I'm working off a Linux server, and although most of the app would be made in PHP, I'm not completely averse to the compilation-performance hit I'd take by calling-out to a Perl script.
I'd rather not use something that involves compiling, as it's a host's server and I don't have access to gcc. I've heard both "yea" and "nay" on just concatenating the actual MP3 files together.