Without mentioning any names (I’m far too polite for that!), a client shared with us that an employee of a competitor essentially said that “web applets are slow” while trying to dissuade them from going with our product.
This misinformation may seem to “ring true” to your average technology user. Or even your more knowledgeable technology user if that employee believed it himself:
An applet “lives” inside the browser to a certain degree, so I can only guess that this person assumed the applets are using the de facto standard transport of the web, HTTP. HTTP is based on TCP/IP and is therefore subject to some pretty serious slowdowns with high bandwidth and/or high latency. If our applets used HTTP (side note: they actually CAN use HTTP as fallback for reliability and guaranteed connectivity) then I could understand the claim. But they don’t. When making an accelerated connection to a FileCatalyst Server, they use UDP.
In the case of applets, the browser is just a “container” or a vehicle for retrieving and executing an application. Instead of downloading, installing, and double-clicking an icon to run (as per a desktop application), the applet downloads automatically via a webpage, requires no installation, and also runs automatically. This is a benefit for scenarios in which a zero-installation solution is required! The applet uses the exact same code base for as any of our other clients (note: other features differ) in order to complete a fully accelerated transfer via UDP.
Applets are applications, too!
Need more proof? Request a demo!