Loading ...
Sorry, an error occurred while loading the content.

Re: [rss-public] Re: Are enclosures downloaded or linked?

Expand Messages
  • Lucas Gonze
    By the way, this goes to the general issue of what the point of the enclosure element is. It s convenient for pre-fetching for offline use in a portable
    Message 1 of 15 , May 29, 2008
    • 0 Attachment
      By the way, this goes to the general issue of what the point of the
      enclosure element is. It's convenient for pre-fetching for offline
      use in a portable device. But in an online context HTML is a lot more
      sensible.

      On Sun, May 25, 2008 at 10:35 AM, Lucas Gonze <lucas.gonze@...> wrote:
      > You could use SMIL in Quicktime to do the metafile. That's probably
      > worthwhile because the Real installed base is so low now. But then
      > again, you could also have a Flash embed in the description and it
      > would work out the same way.
      >
      >
      >
      > On Sun, May 25, 2008 at 4:29 AM, WWWhatsup <joly@...> wrote:
      >>
      >> The problem would be that there is no way within rss to give
      >> people multiple media choices within one feed
      >>
      >> One just makes a different feed.
      >>
      >> Like, in my case, 1) 'podcast' is the the heavy footprint push, while 2) 'update' is the light
      >> footprint pull.
      >>
      >> In the latter the enclosure being a metafile.
      >>
      >> I use realmedia because one can use a metafile that still utilizes http to deliver the file.
      >> A quicktime 'reference movie' would require a quicktime server.
      >>
      >> But most people subscribe to the podcast.
      >>
      >> Recently I have been shooting more jazz, a lot of which is longform as agaonst
      >> the 5 minute songs that comprise most of my material. I've not been including them in the podcast
      >> because I don't want to dump an unexpected couple of 100MB on the unsuspecting subscribers -
      >> that would be a n example. Obviously discrimination based on size could be built into a reader, but
      >> another solution would be if publishers could classify enclosures, e.g. essential, non-essential, short form, long-form,
      >> opt-in etc, even via their own mini-schemas, that would control what actually gets grabbed by readers.
      >>
      >> joly
      >>
      >>
      >> At 11:05 2008-05-24, you wrote:
      >>>Joly,
      >>>I don't understand the problem. Can somebody write blog entry that
      >>>describes the problem with sample RSS showing the problem and the
      >>>solution?
      >>>Thanks,
      >>>
      >>>Randy
      >>>http://www.therssweblog.com
      >>>
      >>>Related: Does anybody have an update on MRSS namespace issue? Is
      >>>Yahoo! ignoring the problem?
      >>>
      >>>--- In rss-public@yahoogroups.com, WWWhatsup <joly@...> wrote:
      >>>>
      >>>> I think this is not a bad idea.
      >>>>
      >>>> I'm a video podcaster. Currently I run two seperate feeds
      >>>> 1) podcast: m4v for ipod
      >>>> 2) update: text + .ram (realvideo metafile)
      >>>>
      >>>> precisely to work around this problem
      >>>>
      >>>> I tried using the MRSS alternative feed syntax in the early days
      >>>but it didn't seem to work well
      >>>> or have much adoption so I dropped it.
      >>>>
      >>>> Joly MacFie
      >>>> http://punkcast.com
      >>>>
      >>>>
      >>>>
      >>>
      >>>
      >>>
      >>>------------------------------------
      >>>
      >>>Yahoo! Groups Links
      >>>
      >>>
      >>>
      >> ---------------------------------------------------------------
      >> WWWhatsup NYC
      >> http://pinstand.com - http://punkcast.com
      >> ---------------------------------------------------------------
      >>
      >>
      >> ------------------------------------
      >>
      >> Yahoo! Groups Links
      >>
      >>
      >>
      >>
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.