Scroll Top

Application Programming Interface (API)

Developing a distributed application with a real-time graphical user interface is often a challenging problem. Before data can be graphically displayed, it must reside on the graphics workstation. Ordinarily, users must manage the acquisition or distribution of the data across the network, requiring network communication protocols. Sammi solves this problem by providing built-in, out-of-the-box networking capabilities through an API.


The API manages all network connectivity and communications between a distributed application and a GUI. Using TCP/IP and Remote Procedure Calls (RPCs) internally to handle data transmission and conversion, Sammi’s API eliminates the need to write network interface code, implement peer or server protocols, manage address name spaces or deal with machine-dependent data type issues.

The bottom line is that when you create an application integrating the Sammi API you have the ability to send (and receive) data to any Sammi Runtime on your network. More importantly, the Sammi API will enable your application to talk to Runtimes on different types of machines. For example, your data acquisition application may reside on a Solaris Sparq 64 bit machine, but your Runtimes are on RedHat Linux 32 bit machines – no problem. The Sammi API will take care of all of this for you. To connect a Sammi Runtime to an application integrated with our API, all you need is a basic hosts type file telling Sammi where on the network the Runtime and application is running. Of course there is no limit to the number of Runtimes and back-end applications. You can have many Runtimes connected to a single application, vice versa or a mix of both if needed.

The Sammi API reduces time to deployment through its data centric programming mode.

Sammi’s data centric framework handles networking and graphics management automatically.

The event loop enables updates to graphics as needed, does not waste cycles updating unchanged graphics.