The content you're reading is getting on in years
This post is on the older side and its content may be out of date.
Be sure to visit our blogs homepage for our latest news, updates and information.
This is a part of the blog post series that explain the new streaming
API for Sitefinity 3.7 SP3. You can view the TOC in the first blog post.
I talked about the API of streaming, explained why it was needed and some of its limitations. Now, I will give more information about limitations.
First, let me define what I mean by corner case, or an exception. Although we tried not to load the whole binary data in memory, there are some places where it is impossible to do so. These rare cases, when the whole binary data is needed, I call corner cases.
When in the Images & Documents module, some information is needed that requires the whole binary data. For example, the image header is checked to ensure that the image type is appropriate (of the allowed types - jpeg, png, etc.).
To resize an image, we need the whole binary data in memory. This applies to uploading images and downloading resized images - like thumbnails or by specifying width and height query string parameters.
While the thumbnail generation is done in DexterLib via streams, a thumbnail image still needs to be saved. Saving thumbnails works in with byte.
Data is sent & received by finite data structures. In other words, we receive a byte. Streaming will work as expected, but will load the whole media object in memory and the wrap it further in MemoryStream.
By showing you these corner cases is I have completed the blog post series about the new Streaming API in Sitefinity 3.7 SP3. I believe they will let you make informed decisions when writing your own streaming provider.
View all posts from The Progress Team on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Subscribe to get all the news, info and tutorials you need to build better business apps and sites
Copyright © 2019 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.