Desktop, Web & Mobile Clients (Concept) provide multiple deployment options for accessing runtime displays, from high-performance desktop applications to zero-install web browsers across all platforms. Client Types, deployment options:

  • Desktop (Windows stations)
    • Rich Client - Desktop application
    • Smart Client - Click-once deployment 
  • Web & Mobile  (HTML5) - Browser-based
  • API Clients - API-based data access

On this page:

  

Overview  →  Architecture | Technology | Differentiators | Solution | Pillars | Editions

Technology → Real-Time Tag Database | Unified Namespace | Native Drivers | UI Technologies

UI Technologies → Clients | Responsive | Layouts | Canvas & Dashboards | WebAssembly


Client Comparison

FeatureRich ClientSmart ClientWeb HTML5
PlatformWindows/LinuxWindows onlyAll platforms
InstallationLocal installClick-onceNone
PerformanceHighestHighStandard
Task SwitchingCan blockCan blockCannot block
UpdatesManualAutomaticImmediate
RedundancyAutomaticAutomaticManual
ThreadingMultiMultiSingle
Port3101 (WCF)3101 (WCF)80/443 (HTTP)

Rich Client

Desktop application with maximum control and performance.

Client Types - Rich Client

Characteristics

  • WPF-based on Windows
  • Runs as standalone application
  • Full Windows integration
  • 64-bit on top of NET. 4.8

Advantages

  • Block Windows task switching (Ctrl+Alt+Del)
  • Automatic redundant server failover
  • Highest performance
  • Full security control

Requirements

  • FrameworX installation
  • Windows OS
  • Network access to server

Deployment

Program: TRichClient.exe (64-bit)
Port: 3101 (configurable)
Technology: WPF

Web Client (WebAssembly)

Browser-based access with zero installation.

Client Types - WebAssembly Client

Characteristics

  • WebAssembly technology
  • Cross-platform compatible
  • Responsive design
  • Touch support

Advantages

  • No installation required
  • Works on any device
  • Immediate updates
  • Platform independent

Limitations

  • Cannot block task switching
  • Single-threaded execution
  • HTTPS communication overhead
  • No direct local file access

Deployment

http://<ServerIP>/html5
or
https:// if certificate is installed



Smart Client

One-click deployment with automatic updates.

Client Types - Rich Client

Characteristics

  • ClickOnce technology
  • Self-updating from server
  • No local installation
  • Runs like Rich Client

Advantages

  • Single-click deployment
  • Automatic updates
  • No IT deployment needed
  • Same features as Rich Client

Requirements

  • .NET Framework 4.8
  • Compatible browser (*)
  • Windows OS only

Deployment

http://<ServerIP>/smartclient
or
https:// if certificate is installed

Browsers Compatible with ClickOnce

Historically, only Internet Explorer (IE) ever had built-in ClickOnce support.

  • ClickOnce was a Microsoft deployment technology (introduced with .NET 2.0) that allowed launching and installing Windows apps directly from a link (.application file).

  • IE could recognize and execute those files without add-ons.

Browsers that require a plugin/extension

  • Microsoft Edge (Legacy / Chromium)

    • No native support.

    • Possible with the “ClickOnce for Microsoft Edge” extension (Microsoft-published).

    • Extension is available in the Microsoft Edge Add-ons store.

  • Google Chrome

    • No native support.

    • Possible with the “Meta4 ClickOnce Launcher” or “ClickOnce for Google Chrome” extension.

    • Extensions pass the .application file to the local ClickOnce handler.

  • Mozilla Firefox

    • No native support.

    • Possible with the “FFClickOnce” add-on (popular for years).

  • Other browsers (Opera, Safari, etc.)

    • Generally no plugin support for ClickOnce.

    • Workarounds involve downloading the .application file manually and running it with the Windows ClickOnce runtime.

    • Not recommended, the RichClient installation is better in this scenario, or the web client.


Runtime Architecture

Server Components

ComponentFunctionDefault Port
TServerCore engine-
Client ServerServes displays3101
Web ServerHTTP access80/443
Tag DatabaseReal-time dataIn-memory

Deployment Considerations

Client Type Deployment Considerations

Rich Client Deployment

Best for:

  • Control rooms
  • Dedicated operator stations
  • High-security environments
  • Maximum performance needs

Smart Client Deployment

Best for:

  • Office environments
  • Remote Windows users
  • Frequent updates
  • Simplified IT management

Web Client Deployment

Best for:

  • Mobile access
  • Cross-platform needs
  • Occasional users
  • Internet/WAN access

Security Features

FeatureRichClientSmartClientWebClent
User Authentication(tick)(tick)(tick)
Task Switch Block(tick)(tick)(error)
Encrypted Comm(tick)(tick)HTTPS
Sandbox Mode(error)(error)(tick)
Certificate Auth(tick)(tick)(tick)

Auto-Start Configuration

Windows Auto-Start

Create shortcut in Startup folder:

Rich: C:\Program Files\FrameworX\TRichClient.exe
Smart: http://server/TSmartClient.application
Web: http://server/html5/index.html

Command Line Options

TRichClient.exe /server:192.168.1.100 /solution:MyProject

Performance Guidelines

Rich/Smart Clients

  • Multi-threaded execution
  • Local graphics acceleration
  • Binary communication
  • Cached resources

Web Clients

  • Single-threaded JavaScript
  • Browser rendering engine
  • HTTP overhead
  • No local caching

Troubleshooting

Connection Issues:

  • Verify server port access
  • Check firewall settings
  • Test network connectivity
  • Review server logs

Update Problems:

  • Clear browser cache (Web)
  • Reset ClickOnce cache (Smart)
  • Reinstall client (Rich)

Performance Issues:

  • Check network latency
  • Monitor server load
  • Verify client resources
  • Review display complexity


In this section...