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:
- Web & Mobile (HTML5) - Browser-based, not install required
- Desktop
- Rich Client - Desktop Windows application
- Smart Client - Click-once deployment
- API Clients - API-based data access
On this page:
Client Comparison
Feature | Rich Client | Smart Client | Web HTML5 |
---|---|---|---|
Platform | Windows/Linux | Windows only | All platforms |
Installation | Local install | Click-once | None |
Performance | Highest | High | Standard |
Task Switching | Can block | Can block | Cannot block |
Updates | Manual | Automatic | Immediate |
Redundancy | Automatic | Automatic | Manual |
Threading | Multi | Multi | Single |
Port | 3101 (WCF) | 3101 (WCF) | 80/443 (HTTP) |
Rich Client
Desktop application with maximum control and performance.
Client Types - Rich Client | |
---|---|
Characteristics
| Advantages
|
Requirements
| Deployment
|
Web Client (WebAssembly)
Browser-based access with zero installation.
Client Types - WebAssembly Client | |
---|---|
Characteristics
| Advantages
|
Limitations
| Deployment
|
Smart Client
One-click deployment with automatic updates.
Client Types - Rich Client | |
---|---|
Characteristics
| Advantages
|
Requirements
| Deployment
|
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
Component | Function | Default Port |
---|---|---|
TServer | Core engine | - |
Client Server | Serves displays | 3101 |
Web Server | HTTP access | 80/443 |
Tag Database | Real-time data | In-memory |
Deployment Considerations
Client Type Deployment Considerations | ||
Rich Client DeploymentBest for:
| Smart Client DeploymentBest for:
| Web Client DeploymentBest for:
|
Security Features
Feature | RichClient | SmartClient | WebClent |
---|---|---|---|
User Authentication | |||
Task Switch Block | |||
Encrypted Comm | HTTPS | ||
Sandbox Mode | |||
Certificate Auth |
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...