Here's how our architecture hangs together:
The icons, images and glyphs used by KeyLines are hosted on your servers. We can provide icon sets but you are free to choose your own too.
In a modern browser, KeyLines uses HTML5 Canvas for rendering. For older browsers - IE7 and IE8 - KeyLines uses Adobe Flash, which is already widely installed across PCs.
The smart thing about KeyLines is that exactly the same API is used in both old and new browsers. The whole issue is abstracted away from your code, leaving the developer free to concentrate on the business logic.
As the end-user interacts with KeyLines, it raises events. Developers can bind to those events to customize the behaviour of the component.
For example, by binding to the 'contextmenu' event, a developer can create a right-click menu for items on the chart.
Other events include 'hover' (for tool-tips), mouse clicking and keyboard presses. The SDK has many examples showing how these events can be customized.
KeyLines can be hosted by any web server - whether J2EE, .NET, or anything else. All KeyLines needs is to be embedded on the web page.
You are free to define your end points, MVC patterns and authentication choices in your favourite framework.
One key advantage in the KeyLines architecture is that there is no need to deploy visualization servers.
Some visualization vendors render content on the server-side and this can lead to difficulties:
- Pushing images across the wire uses more bandwidth and can lead to higher latency
- Visualization servers need to be purchased, configured and maintained - which costs more money
- Additional servers may be needed at peak times or if the load increases
Our approach is much more scalable: processing for graphics is done client-side, meaning that the architecture can be simpler, the server costs are minimised and capacity is easier to plan. Furthermore, our components are simple, self-contained and easy to drop into a web application.
No applet required
The traditional way of visualizing data in a browser is to use Java applets.
Java applets were invented back in the 1990s and suffer from known security issues. The user experience isn't great because users have to accept a security warning. And loading the applet can take ages.
HTML5 gives better security: code runs in the browser sandbox. And there is no need for the user to click OK in a dialog or wait for the JVM to load.
Security and hosting
KeyLines is designed to be hosted on your own servers inside the corporate firewall. KeyLines never 'phones home' - it does not require any connection outside your firewall. It is totally self-contained. .
KeyLines is also suitable for extranet or even public deployments. The transport layer can be SSL encrypted with HTTPS end-points for both the KeyLines component, the data loaded, and the assets.
Why not contact us to arrange a demo?