OSMF v0.93 available

We’re very excited to announce that the Sprint 10 drop, OSMF version 0.93, is now available. And we’re even more excited to announce that our APIs are locked down for 1.0 (more on that below).  If you’ve been waiting for the dust to settle before diving into OSMF, then you should take a look at the v0.93 release.

Although this release has primarily been about API lockdown and stability, there are a few new features worth calling out:

  • DVR Support.  OSMF now supports DVR via Flash Media Server’s server-side DVRCast application.  This feature allows clients to jump back in time while viewing a live stream.
  • RSS + MRSS.  Via a new AS3 library, OSMF can now parse all of the major feed formats, plus the media-centric RSS extensions.
  • Extended HTTP Streaming Support.  OSMF now supports subclips for HTTP-streamed content, and DRM for HTTP-streamed content.

On the API front, we’ve spent the past six weeks reviewing, debating, and refining the public APIs.  We applied a critical eye towards the APIs, renaming those that were not immediately clear, eliminating those for which not enough use cases existed.  Moving forward, we’re setting an extremely high bar for accepting additional API changes prior to 1.0.  See the API Lockdown Status page for details on this process, and on the API changes themselves.  (Note that this API lockdown applies to the framework-level APIs, not to the APIs for individual libraries or plugins, such as VAST or SMIL.)

And now, to the links:

2 Responses to OSMF v0.93 available

  1. greg•h says:

    Regarding API Lockdown Status, can you provide more clarification please?First, the wiki page referenced for “API Lockdown Status” has changed its format and the nature of it’s content. When the “API Lockdown Status” page was originally created with the Sprint 9 release, it simply listed all packages and their lockdown status. I found this package-by-package status very helpful. Could you perhaps provide an update for Sprint 10 once again providing the package-by-package status?Second, the current format seems more like a riddle. The riddle starts with “clues” like “What Constitutes Public APIs” and “What Does Not Constitute Public APIs” and then leaves it to the reader to deduce what is what. The remainder of the page currently is now a version change release document (“API Changes in Sprint 10”) without, however, simply stating status package-by-package. Back to my first point, could you please just spell out the status package-by-package?Thank you again for all of your great work in creating this awesome new ecosystem for video and other rich media delivery!Best regards,g

  2. Brian Riggs says:

    There’s no package-by-package status because everything is 100% reviewed. (The two exceptions called out in the page, logging and MediaErrorCodes, have been temporarily removed from the public API.) I’ve made a few minor edits to clarify some points, but I’m reluctant to include the package-by-package status (which would say “100%” for all packages) because I don’t want to imply that any of the public APIs are still in flux.