JRD provides the foundation for turning any client device, thin or fat, into an ultra-thin Java Terminal. Its client is much smaller than a Java Virtual Machine, and it requires much less computing power. JRD has an open architecture and can be ported to different platforms. JRD is suitable for a wide range of devices, from small embedded devices that can not even hold a Java Virtual Machine, to large systems such as PCs and workstations.

• JRD is the first technology to enable Java GUI applications to be accessed anywhere through a web browser.
• JRD is the first technology that allows a client machine without a Java Virtual Machine to access a remote Java application. Traditionally, JVM is a must to run a Java application.
• JRD can be utilized to make web sites dynamic and interactive with functionality same as Java applets, but in a different way that combines the good features of Java applets and CGI (Common Gateway Interface). CGI allows a web page to take user inputs and invoke a server side application to process them. Since CGI runs remotely on the server side, it is secure and easy to administer. However, its interface is limited by HTML forms. Java applets, on the other hand, brings richer GUIs to web pages. An applet is downloaded from a web server and then runs on the browser computer. A Java Virtual Machine is required on the local computer. JRD technology combines the good features of CGI and applets. It brings the same functionality of Java applets, but it runs on the server side as CGI does. In other words, you can consider JRD as server side applet.
• JRD allows a securer and easier distribution of software programs. Since JRD is running on the server, it is easier to update and manage. For an instance, you do not need to worry about what version of the Java Virtual Machine is running on the client because it does not require one. Since there is no downloading, people have no way to access your software code which protects your intellectual property, especially in the case of Java where de-compilation and reverse engineering is easy. Secondly, JRD requires much less computing power on the client, and has no need for a Java virtual machine, on other hand, since applets run locally at the end user’s machine, and thus it requires certain computing power and Java-enabled features on the client side. Thirdly, it will substantially save your development efforts. Through JRD, services can still have rich GUIs, but the programming model is much simpler. Software is developed as if it would be used wholly on a single machine. JRD sends graphic displays to end users, and also takes inputs from end users. The service is run on the server, and there is no need to download any application code. We predict JRD will be popular than Applet in some situations such growing mobile computing devices.
• JRD made it possible to turn any device, thin or fat, to become a Java Terminal. The very small size of JRD will be important in small devices where a JVM is too much a load. With JRD, many devices, such as cellular phones, set-top boxes, can become terminals for Java applications.