Last year I wrote a somewhat humoristic post about the importance of defaults and not asking end-users for information they are not equipped to provide. As an example of this I described the PowerTerm WebConnect client download and installation mechanism and explained that, unlike other client installers, it does not require end-users to provide any configuration settings such as the server address. The PowerTerm WebConnect client download mechanism has several additional features and capabilities one of which is that it only downloads those components that are actually required by the specific end-point device. Moreover, it downloads these components on-demand, if and when they are needed. This results in the smallest possible download size - my laptop is (still) running Windows XP SP2 and the total size of the PowerTerm WebConnect client downloaded to it is 1.8MB.
I’m describing this mechanism because I just read that the size of the latest version of the Citrix ICA Client (v10.2) is a whopping 14.9MB. This means that it’s 828% the size of the PowerTerm WebConnect client downloaded to my computer! (Apparently it’s also substantially larger than previous Citrix versions.) But is this huge difference in the download size still important in this day and age of broadband and fast corporate networks? In my opinion the answer is a definite yes, it is very important. One reason that it is important is that not every remote or roaming user will be connected via a fast network connection. I’ve encountered a number of situations where such a large client would mean an unacceptably lengthy client download period.
Potentially more significant is the communication overhead involved in provisioning the client to every end-point in the corporate network. For example, if there are 5,000 end-point devices then at least 72.8GB need to travel through the network every time the Citrix is updated! The PowerTerm WebConnect downloader, on the other hand, will only update the components that have actually changed, so the network overhead may be as low as 4GB in the same scenario.
It is worth mentioning that the PowerTerm WebConnect client can also be installed as a standard MSI. The size of this MSI is 3.3MB - still significantly smaller than the Citrix client.
Sunday, March 23, 2008
Subscribe to:
Post Comments (Atom)



7 comments:
Please compare apples to apples. The Citrix web client is much smaller than the 32 bit client that you reference in your article.
I believe I am comparing apples to apples because:
1. The PowerTerm WebConnect client provides features such as:
a. Rich client interface with auto-update
b. Local desktop integration
c. Remote assistance and support
d. End-point performance monitoring
2. The latest version of the Citrix client is twice as large as previous versions of itself.
Again, you are not comparing apples to apples. There is even a tool so you can pick and choose which features you want to have within the client. An admin can bring the Citrix web client to around 400K if size is what matters.
Please don't start comparing features and functionality because you won't win that game! :)
My point was simple: the PowerTerm WebConnect client is not like the Citrix web client - it is a full-blown rich client.
I do agree that having a web client that can be trimmed in size can mitigate the problem, but I still think that a 15MB client is way too much.
Oh, and we are not out to win a features race. We want to win on usability and ROI.
The Citrix web client is a rich client. I am using it now and it is fantastic!!
Actually I made a mistake - the Citrix Client is fat and lazy - you are right I should eb using the Ericom Client
Hi Dan,
Maybe next time the other anonymous can explain it better?
;-))
Post a Comment