This project is read-only.

Podcast Upload | Ending basic HTTP upload support

Oct 29, 2008 at 4:38 AM

With the official release of Silverlight 2 RTW and the enhancements being made to the PKS Silverlight upload control, the team is planning to end support for the basic HTTP ASP.net upload mechanism in future releases. The horizon for this change is the December or January release, more information will be communicated as the release features are finalized.

We are confident this is the right approach, as the Silverlight control offers a far superior user experience, allowing users to pause and resume uploads and select and designate multiple files. From the technical standpoint the control offers a faster and more reliable upload experience than that of the basic HTTP upload. 

However before making the final decision, we want to better understand the potential impacts on the current implementations.

Thanks for your support in PKS and Happy Podcasting!

Oct 29, 2008 at 11:48 AM

Hi there,

This would have an impact on our installation.  We're currently working on the September release, and making several changes to it, including the addition of a third part media trans-coding product, the use of Flash instead of Silverlight, various branding changes and other security changes for regulatory compliance.

One of the key items is that we're using Flash to deliver the video content as Silverlight isn't part of our client's desktop software (160K machines).  This means that we are planning on using the HTTP upload mechanism.

Clearly for us, an alternative would be to develop or re-use a component to upload files using Flash instead of Silverlight.  A quick google indicates there are several around.

What I would be interested to know is what makes the Silverlight control more reliable in terms of the file transfer experience?

It would be good if you could share with the community some more information about the two approaches?

Best regards,

David.

Oct 31, 2008 at 6:07 PM

Hi David,

I think your approach of creating / leveraging the Silverlight upload control to create a Flash upload control is the right direction.

As far as the advantages, the Silverlight control can be restarted if there is a network error, it has a better UI look and feel, but it requires Silverlight to be installed on the client.

 

HTTP has no restart capability in case of a network error.  If your file is lost midstream the item will have to restart from the beginning, but it requires no client software.

Thanks,
Austin