Writes Jon Udell in InfoWorld [via Reena]:
The browser is today, and will for some time remain, the dominant way to interact with Web services on the desktop. More accurately it’s a platform that supports many different modes of interaction. Cloud-based SOAP clients can reflect data into the browser as HTML. The browser can host Java, ActiveX, Flash, or other kinds of components that make SOAP calls; or the browser itself can make SOAP calls using its built-in script engine. The browser can also suck in raw XML data and process it locally, perhaps even while offline, using built-in parsing and transformation engines.
Adds Udell: “The browser makes a poor digital dashboard. SOAP-enabled Office, Win32, Java, .Net, and Flash clients can be more effective, and these avenues are being explored. Also, vendors such as Altio, Digital Harbor, and Fourbit are pioneering a new kind of “smart-client” technology: A Java-based run time, deployed to the desktop, fetches XML descriptions from the network and renders them as interactive GUI applications with widgets that talk locally to one another and remotely to Web services. Because they are purely XML-driven, the Java rendering engine could (with some elbow grease) be replaced with a .Net (or other) renderer.”
desktop digital dashboard