News

Microsoft To Add Smooth Streaming in IIS7

Web sites will be able to get improved bandwidth management for streaming media using a new extension to the Microsoft Internet Information Services 7.0 (IIS7) Web server. The extension, announced last week, is called "IIS Smooth Streaming."

The technology for Smooth Streaming is derived from Microsoft's Silverlight multimedia platform, according to Scott Guthrie, Microsoft's corporate vice president of the .NET Developer Division.

Smooth Streaming will be available in beta release early next year, the Swiss MSDN Team Blog explained on Monday. IIS Smooth Streaming will be a free extension to IIS7.

Microsoft Expression Encoder 2 SP1 also will support IIS Smooth Streaming with encoding and publishing functionalities, Microsoft announced last week.

The new "intelligent streaming media feature" will dynamically adjust the video quality of a media file playing on Microsoft Silverlight in real time, based on bandwidth and CPU throughput.

Users with high-bandwidth connectivity will be able to receive high-definition playback when Smooth Streaming is enabled. Those with lower bandwidth connections will benefit from a delegated streaming speed. Both will "enjoy a consistent, high-quality streaming experience," according to the blog post.

Services using the IIS Smooth Streaming extension will be offered in a beta trial early next year by Akamai Technologies Inc. The Cambridge, Mass.-based company provides multimedia support for social networking portals, professional sports organizations and other companies. Akamai's servers support "20 percent" of all Web media, according to company literature.

In a joint press release issued last week, Microsoft and Akamai said that the new adaptive streaming technology was "developed, tested and proven" while delivering streaming Web videos from the 2008 Beijing Olympic Games. The broadcasts used Microsoft's free Silverlight client.

Smooth Streaming uses standard HTTP requests and responses to optimize rich media delivery to Silverlight, according to a blog post by Microsoft's John Bocharov.

"Unlike competing streaming solutions, delivering Smooth Streaming to clients does not require investing in deploying, configuring, and managing a swarm of proprietary distribution servers," Bocharov stated in the blog. "IIS Smooth Streaming was created with scalability and HTTP cacheability as first-class design goals, to help our customers minimize the cost per megabyte delivered."

About the Author

Herb Torrens is an award-winning freelance writer based in Southern California. He managed the MCSP program for a leading computer telephony integrator for more than five years and has worked with numerous solution providers including HP/Compaq, Nortel, and Microsoft in all forms of media.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube