Application Virtualization Comparison chart

I already used their first chart from june which helped me a lot choosing the right product at that time for a customer and this chart is even more usefull with sneak previews of what the vendors are working on now !

As far as I know, XenApp start pushing the 1st packet when requested at application launch. The application start to execute even if the entire package is not streamed down completly. BUT, the streaming continue in order to get the full package on the client. There is no sequence that say "Office package, only word requested, word pushed and I'm waiting for escel request to stream the rest'"... It is more "word requested, word streamed then I take this opportunity to contiue and stream the rest". Once discussed with Citrix Rep, he said it is because they want to be sure when off line to get the entire application package and not just a sequence.

In addition, I was quite sure that Citrix had a x64 profiler for x64 applications... Have to check it.

Any way,  it didn't remove anything to the quality of this document which help to compare and, as stated in page 4, to prepare to choose "the products yourself in a proof of concept before making a definitive choice".

The Profile may be stored in a .cab file but it is never transported across the network to the client as a large file. When an applicaiton profile is created it associates each appliactions with the file it needs to initially launch. This file is streamed down to the client on initial launch and then additional files are streamed on demand.

This means that when (for instance) launch Word the streaming client fetches and starts running winword.exe (there is also a bit of stuff pulled down early like fonts), then starts grabbing DLL's as needed based on the features you use. If you never hit the clip art gallery, it never downloads any clip art.

As far as the protocol goes Streaming has traditionally used CIFS to copy those individual objects, but HTTP(S) is supported now with the release of XenApp 5. Honestly the difference in delivery time between using these methods, which are already familliar on most WAN's, is not noticibly slower than the RTSP that SoftGrid choose. It is much easier to support and troubleshoot CIFS and HTTP though and you don't have to install anything extra to turn a branch file server into a Streaming Profile repository.

Hi Shawn,

We tried our best to be as accurate as possible. It was hard though because not all vendors calls the features the same and/or the features don't always work the same way. Please share your knowledge about the inaccuracies, so we can update the chart if necessary.

Regards,

Sven Huisman (http://virtualfuture.info)

doest support 64bit applications, and has done that for a long time now.

So please upgrade the chart.

Regards

the IT KING