How Effective Is Stocrin

Wireless Client side integration

Sometimes they come back. 3270 terminal emulation to the pre-Windows DDE OLE up to much today mashup "Web 2.0".

When it comes to integration we think almost solely to the issue back-end, or Web Services, or BSE.

rarely discusses the problem of the client side, or the need to build applications that aggregated user interfaces separate.

This is because each application typically implements a specific feature.

The integration is achieved in the "back end" through the exchange of data, at best through the exhibition of "services" centralized.

The "front end" but is almost always implemented from scratch, usually using technologies based on components that, although advanced in years and more and more productive, requiring the subject to artire almost from scratch.

This is an obstacle to actually implement a services-based architecture, first of all because every time to rewrite the "front end" that is expensive partly negate the anticipated benefits of a Service Oriented Architecture ", not counting that the need to rewrite the presentation logic gate made to code duplication and potential disalinneamenti between systems.

In practice this leads to the fact that still many "silos" separate and redundant applications

A possible solution is the integration of components including client, built with technologies and approaches.

A first approach might be called "black box" is what provides for the integration of systems using the GUI user interface (Web or Fat Client others) by "robots" which reflect the interactions of a user "human "(via keyboard and mouse input and output via reading of the data presented on the screen).

This solution, the strength of frameworks like Microsoft Customer Care Framework, has among the strengths of its speed of construction and especially the ability to integrate applications legacy of which you can not or do not want to make any changes.

However this integration strategy is inherently extremely "fragile" in the sense that even a small change to the GUI of the integrated system can lead to abnormalities difficult to trace and fix.

Components on Client

in some ways the opposite approach also provides the user interface is based on services, or rather on components, reusable and extensible.

There is not yet a mature technology, certainly a good example is the Descriptio Resource Framework (RDF) that, among other things, would allow the opening and above all the standardization of components based on Web Client

Meanwhile, there are technologies that are still in an embryonic state, but certainly interesting.

Microformats

I microformats such as Web pages can be incorporated in "standard" RDF information in order to gradually begin to exploit the advantages of this tecologia still in the process of maturation.

Mashups

I mashups are not in fact a real technology, but a number of disparate solutions that share from the "open" that is based on technologies "Open" or public domain, for example gooogle Maps allows the integration of services Please use a component model based on JavaScript.