Servoy 2020 Documentation
Child pages
  • Web Client
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Starting Servoy Web Clients

Servoy Web Clients run in a browser and can be started by accessing a URL on the Servoy Application Server.

Solution Select page
<serverUrl>/servoy-webclient
Deeplink into specific solution
<serverUrl>/servoy-client/ss/s/mySolutionName
Specify the method to execute on startup
<serverUrl>/servoy-client/ss/s/mySolutionName/m/myMethodName
Specify startup argument
<serverUrl>/servoy-client/ss/s/mySolutionName/a/value
Specify the method to execute & startup argument
<serverUrl>/servoy-client/ss/s/mySolutionName/m/myMethodName/a/value
Specify the startup argument & named arguments
<serverUrl>/servoy-client/ss/s/mySolutionName/a/value/name1/value1/name2/value2
Specify the method to execute, the startup argument & named arguments
<serverUrl>/servoy-client/ss/s/mySolutionName/m/myMethodName/a/value/name1/value1/name2/value2

Short vs. long syntax

The urls above use the short syntax. Instead of using the short syntax, the following mapping allows using the longer syntax:

  • ss > solutions (Web Client only)
  • s > solution (Web Client only)
  • m > method
  • a > argument
Running Servoy Web Client inside a Frame or IFrame

When running a Servoy Web Client inside an Frame or IFrame and the domain of the page into which the frame is embedded does not equal the domain from which the Web Client is hosted, there is a possible issue with the ability of storing HTTP Cookies.

Internet Explorer, by default, disallows the storage of Cookies from withing the Frame/IFrame if the domains of the page hosting the frame and the page inside the frame do not match.

By default Servoy Web Client uses HTTP Cookies to save the position and location of dialogs. Also the functions application.setUserProperty(...) and application.getUserProperty(...) utilize Cookies in the Web Client.

If no dialogs are used in the application and User Properties are not used, there is no issue. Also, when the page hosting the frame and the page inside the frame are hosted from the same domain (for example http://www.mycompany.com) there is also no issue.

However, if dialogs or User Properties are used and are deemed important and the domains do not match, extra steps are required to make use that the application will function properly.

Option 1: Altering the Security level in Internet Explorer on every Client machine
By default the privacy level setting of Internet Explorer is set to Medium. This setting can be found under Tools > Internet Options > Privacy tab.

When the level is set to Medium, third party cookies will be blocked. By altering the privacy level to the lowest level "Accept All Cookies" the third party Cookies will get accepted. Although this works, it means that in order to be able to use the Solution properly the setting needs to be altered in the browser of all users. It can be that corporate IT departments restrict the user from altering this setting.

Note: Third party Cookies are Cookies from a different domain as the domain from the main page displayed in the browser.

Option 2: Adding a "Compact Privacy Policy" to the Web Client http://forum.developers.facebook.com/viewtopic.php?pid=204805

http://www.alphaworks.ibm.com/tech/p3peditor http://www.w3.org/P3P/implementations.html

  • No labels