Page History
...
Web Client is a browser-based application of which the UI is rendered in the browser using pure HTML, CSS and a bit of JavaScript for event handling and communication with the Servoy Application Server. The business logic of the Solution that is running in the Web Client is executed on the Application Server for security reasons: the code of the business logic is not exposed in the webpage markup.
Stoc |
---|
Supported Browsers
The Servoy Web Client runs in the last few versions of all modern browsers, like Mozilla FireFox, Safari, Google Chrome and Internet Explorer.
...
Servoy Web Clients run in a browser and can be started by accessing a URL on the Servoy Application Server.
Web Client Start URL | What is does | Comments |
---|---|---|
{serverURL}/servoy-webclient | Opens the 'Select Solution' webpage | The 'Select Solution' webpage will not list any solutions if solution browsing is disabled, see Solution browsing. |
{serverURL}/servoy-webclient/ss/s/{mySolutionName} | Opens the specified solution |
{serverURL}/servoy-webclient/ss/s/{mySolutionName}/a/{value} | Opens the specified solution. The argument value is passed into the Solutions onOpen event handler. |
{serverURL}/servoy-webclient/ss/s/{mySolutionName}/a/{value}/{name1}/{value1}/{name1}/{value2} | The same as the previous scenario, but with additional custom keys for additional arguments |
{serverURL}/servoy-webclient/ss/s/{mySolutionName}/m/{myMethodName} | Opens the specified solution and executed the specified method after the solution is opened |
{serverURL}/servoy-webclient/ss/s/{mySolutionName}/m/{myMethodName}/a/{value} | The same as the previous scenario, but specifying a single value to be passed as an argument into the onOpen event handler and deeplink method |
{serverURL}/servoy-webclient/ss/s/{mySolutionName}/m/{myMethodName}/a/{value}/{name1}/{value1}/{name2}/{value2} | The same as the previous scenario, but with additional custom keys for additional arguments |
Include Page | ||||
---|---|---|---|---|
|
...
As browsers share session information between all their tabs and windows, it's not possible the run multiple Web Clients hosted from the same application server within the same browser.
By default browser sessions will not timeout, no matter what the value is of the the containers/tomcat session timeout, this is because by default we have a databroadcast notifier that polls the server every 5 seconds to see if there is something to report
Embedding a Web Client in an IFrame
...