Extremely fast execution of web pages after one time install. On all subsequent accesses to the page, the already installed component executes immediately after the HTML portion has been loaded.

Instead of interpreting script, compiled code does the work. Execution is therefore 100’s of times faster.

Numerous data pipes can be set up by the component back to the server to retrieve any type of available information including database data, images, documents, spreadsheets, audio, video and more.

Data can be transmitted in binary and compressed to provide speed and security. Alternatively, data can be transmitted as XML.

Zero deployment issues. There are no setup disks or CDs to create and distribute. Simply putting a new version of the HTML page and component onto the server gives all users access to it the next time they request the associated web page.

Any number of development languages can be used to create a component including VB, C++, etc. This means that an organization can leverage its existing client/server programming talent.

Components have all of the programmatic resources that were available in traditional distributed applications and far surpassing the capabilities of client scripting.

Since the business logic is compiled, it is not available for viewing via the ‘View Source’ browser menu thus better protecting your code investment.

Since business logic can be included securely into the component on the client, state does not need to be maintained for it on the server. This results in a truly scalable system.

A request is received for a web page by a server, which sent it to the client’s browser. The browser notes that there is an attachment and requests that the server send it as well. Once received, the browser decompresses the file and installs a component. On subsequent accesses, the browser again notes that there is an attachment, but having already installed it, checks its version. If the version has not changed, no request is issued to the server for the component and execution on the client begins immediately. Should the browser note a difference in the version that it has already loaded and that of the one on the server, the request for the new replacement component will be made and it will be installed upon receipt. Once the component is executing, any events occurring on the web page are made available to the component for further processing. The component has the capability to alter the appearance of the web page and to set up multiple links back to the server to request or send data. This component can perform all the capabilities of a traditional CD or floppy installed application.

Very. Application Streaming^tm never sends data via clear text which is often used in web pages. All data is sent in compressed binary format. Transmitting data between a web page and a server in compressed binary does not allow anyone watching your data to understand its contents. As well, compressed binary provides exceptional performance.

Since data transfers occurs via the web page's associated component, the screen does not need to be refreshed or changed by the server. For example, scrolling through a large list does not require a refresh of the screen because the component is retrieving additional data from the server in the background and filling it onto the existing screen giving the web page the feel of a traditional client/server application.

Any kind of data will work. This can include audio, video and database data. The types of data are limited only by the application’s needs.

Currently, only computers operating Windows operating systems and Internet Explorer 5 or higher are supported. Additionally, there are some settings in the browser that may need to be enabled, if not already. These deal with connectivity issues. Because of this, a consumer based site cannot assume that all computer/browser clients will be set correctly for this technology to work and this technology is therefore targeted toward corporate intranet/extranet application implementations.

Since the client component can have all the capabilities of a traditional installed application, it has the ability to manage its own state. As a result the server does not need to perform this function. As many servers as needed can be added to handle the work. Further, by separating and placing the presentation, business logic, data access layer and data repository onto their own physical machines, the achievement of true vertical and horizontal scalability is realized.

  | Back to top |

Request more information about Application Streaming^tm