I took a look again at the guide and I agree there is a place for improvements
I'll suggest corrections for it.
It should work the following way:
1) you build your web application that knows about every user. the application is hosted on "webserver.host" and accepts requests on various "app.js" paths.
2) Parallels HTML5 Client is hosted on "server-name":
https://server-name/RASHTML5Gateway
2) from your portal Parallels HTML5 Client is started in a new tab of user browser using a link "
https://server-name/RASHTML5Gateway/?https://webserver.host/app.js#/launch"
3) The link loads Parallels HTML5 Client and the Client before launching an application (actually before doing anything else at all) connects to "
https://webserver.host/app.js" and expects a JSON reply containing user credentials and remote connection settings:
RASHTML5LoadApp ({ u: 'username', q: 'password', a: '#3', p: 'c:\\temp\\another.txt', extra: { redirectPrinter: true, redirectLinks: true, redirectSound: true } });
a: '#3' - is a publishing ID.
p: - is a parameter to start the app with
app.js - is a way to pass all necessary parameters to your web application. It should be dynamically generated for every user and every application he has access to through your portal. for example notepad_3_username-user123.js or whatever you are comfortable with.
