What is the rationale for moving to intelligent device architectures?
Current Web technology is essentially based on the thin-client paradigm, in which the user terminal is reduced to the browser function and all application logic other than HTML and graphics rendering is living on a server. Any user interaction, however futile, translates into a round-trip to the server and back across the network. Although this model has obvious advantages with regard to application deployment, there are several reasons why this scheme is not viable as a general solution: · It comes with an inherent performance limitation. Whatever the network bandwidth, response times cannot be guaranteed to be instantaneous and are in fact subject to mostly unpredictable variations due to the sharing of the physical network resource by a variable number of devices at any given time. · For reliability reasons, it is generally not desirable that the operation of an individual device be totally dependent on the availability of the network. Instead, a device should be able to sustain aut
Related Questions
- How do I upgrade packages across different architectures by using an RPM bundle on a managed device that has ZENworks 7.3 Linux Management Hot Patch 1 or later installed?
- How do I configure NetVision NPM to collect information from an intelligent network device such as a router or switch?
- What is the rationale for moving to intelligent device architectures?
