Platforms and clients
Platform and language support
| Microsoft .NET | Java | C | |
|---|---|---|---|
| Microsoft/Windows | Complete platform | Toolkit | Toolkit Client/Server |
| Linux | — | Toolkit Client/Server | Toolkit Client/Server |
| Apple | Toolkit – Client | — | Client native application |
| Android | Toolkit – Client | Toolkit Client/Server | Toolkit Client/Server |
| QNX | — | Toolkit Client/Server | Toolkit Client/Server |
Windows/.NET is the complete, first-class platform; other OS/language combinations are available as toolkits, generally client-only or client/server depending on the combination — check the current matrix before assuming full parity across platforms.
OPC-UA compliance
Sinapse is built on the standard OPC-UA stack (UA Application layer over JAVA/.NET/C++/C APIs, over JAVA/.NET/UA ANSI C stacks, over Win32/Linux32/other portability layers, over the OS) — fully OPC-UA compliant to guarantee interoperability at every level, including transparent communication with any OPC-UA-based system regardless of platform (Java-enabled systems, .NET-ported systems, embedded systems).
Mobile and tablet clients
Tablet/Mobile is a distinct, first-class client category in Sinapse's own architecture diagrams — connecting to the Sinapse (multi-server) Message Bus on the same footing as desktop Sinapse Clients and UNIX/embedded clients, not as an afterthought. Two things to keep separate:
- General mobile toolkit reach: per the platform table above, Android and Apple/iOS are supported as client-only toolkits (Android also has a client/server toolkit in Java or C) — a mobile client can run and display the configured interface, but Windows/.NET remains the only platform offering the complete server-side platform.
- Real-world tablet deployment: the Drive Me module is shown deployed on rugged industrial Windows tablets, running the same WPF-based Client Run-Time interface as a desktop client — i.e. on the shop floor, "tablet" in practice often means a ruggedized Windows tablet running the full .NET client, not necessarily an Android/iOS app built from the mobile toolkit. Ask which is actually needed (a native Android/iOS toolkit app, vs. a Windows tablet running the standard client) if it's unclear.
Server and client characteristics
Server: hot update of scripts and execution topology without stopping the service; redundant servers; runs as a Windows service or as a standalone application; native elaboration via CLR or XML; computational load distributable across multiple servers; message-based communication that stays fully transparent across plugin boundaries (a key contributor to overall robustness).
Client: supports multiple simultaneous graphical configurations (different roles/departments can see different interfaces off the same server-side logic — e.g. company director, maintenance department, team leader, and local operator each with a role-specific view); scriptable UI using embedded C#/VB; localizable; interface modifiable using XAML-style markup; user authentication management.