Page History
...
| Include Page | ||||
|---|---|---|---|---|
|
The Servoy Admin page exposes a couple of settings that influence the starting of Smart Clients:
...
Deeplinking into existing Smart Client
When a user already has a Smart Client open, it's possible to provide the user a URL that deeplinks to a method in the open solution. When the URL is opened, it will access the Application Server and the Application Server then contacts the existing Smart Client and executes the specified method.
To enable this deeplinking into existing Smart Clients, the servoy.allowExistingClientActivate setting on the Admin page needs to be set to true. When set to true, if a Smart Client is already opened on
...
the users machine and from that machine
...
the deeplink url is called that specifies a deeplink method, instead of opening a new Smart Client, the method is invoked inside the existing Smart Client.
...
| Note | ||
|---|---|---|
| ||
The deeplinking into an existing Smart Client is partly based on cookies. When starting the Smart Client from, for example a desktop shortcut, while deeplink from within an email in a mail client, it can happen that the first deeplink from the mail client opens a new Smart Client anyway. A possible workaround for this is added '?x=x' to the shortcut's URL, like <serverUrl>/servoy-client/mySolutionName.jnlp?x=x |
Smart Client footprint
A Smart Client has a very small footprint on the client machine. For startup performance reasons, both the Smart Client libraries as well as the Servoy Solution binaries are cached.
...
Overview
Content Tools
Activity