{"id":2134,"date":"2014-09-22T16:59:57","date_gmt":"2014-09-22T20:59:57","guid":{"rendered":"https:\/\/www.tmurgent.com\/TMBlog\/?p=2134"},"modified":"2014-09-22T21:23:07","modified_gmt":"2014-09-23T01:23:07","slug":"on-streaming-and-formats-in-app-v","status":"publish","type":"post","link":"https:\/\/www.tmurgent.com\/TmBlog\/?p=2134","title":{"rendered":"On Streaming and Formats in App-V"},"content":{"rendered":"

On Streaming and Formats in App-V<\/b><\/span><\/h1>\n

Tim Mangan
\nTMurgent Technologies, LLP
\nSeptember 22, 2014
\nRelated Product:\u00a0 App-V 5.0 SP2 HF5 and prior<\/b><\/span><\/p>\n

\"\"When we created the original application virtualization product, SoftGrid, streaming was a very important part of the implementation.\u00a0 Over the years, the streaming aspect has become less important to implementations, while remaining important to the decision makers that choose application virtualization with App-V.\u00a0 What some may not realize is how App-V 5 changed how streaming is done from the previously generation product.\u00a0 This document identifies the differences and suggests that in most cases, streaming should not play such a large role in the decision to virtualize.<\/p>\n

Historical Roots<\/h2>\n

Softricity, which created the original version of App-V called SoftGrid, was born out of another company called SoftwareWow.\u00a0 SoftwareWow focused on Application Streaming for delivery of the applications, but did not virtualize the applications.\u00a0 I joined SoftwareWow in 1999 due to my background as an expert in developing network protocols.<\/p>\n

When we made the change to Softricity to build SoftGrid, streaming remained as one of the core properties of the product value.\u00a0 We led discussions with customers based on three tenants: Centralized Delivery, Streaming, and Virtualization:<\/p>\n