If I were feedburner I probably would have put &filename=origional_file.mov at the end. Just make sure they werent going to break any systems already in place. I agree with you there, it seems a simple safe guard for backward compatability.
On the other hand ...
They're feed makers not really feed aggregators ... It's possible it just never occured to them that some systems might not be acting on the acrual filename but rather a larger portion of the url.
I'm not sure the url system they've used is any more 'silly' than it is to expect them to tack on a query string variable they dont actually need to recieve in order to provide the media.
All that being said, yeah I think it would be great if some standard could be agreed upon such that enclosure redirects should always end with the filename ... why not? Some may chose to use an ending variable such as &filename=origional_file.ext or some might use a more fancy redirect like http://redirecting-service.com/user/filename.ext ... Dont see how such a standard could be a bad thing.
Is this something that microformats might be able to provide?
- Dave
On 3/16/06, Michael Sullivan <[EMAIL PROTECTED]> wrote:
David,
I know, you are correct.
I am not going to argue that frome a technical point of view, these urls can be handled by media aggreators.
I want to debate now whether services like feedburner or any other that alters actual enclosure urls should follow some sort of standard or not.
What do you think?
--
http://www.DavidMeade.com
SPONSORED LINKS
| Individual | Fireant | Use |
YAHOO! GROUPS LINKS
- Visit your group "videoblogging" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
