How does Remote Control work?

The Remote Control process is pre-defined and cannot be customised.

At one end we have TLNplanner internet as a program that can be controlled remotely and is completely browser-based.

At the other end is a remote-controlling instance that could take the form of a browser (for example).

Note:  TLNplanner internet can only be opened in the route planning use case using Remote Control.

 

 

• Step 1

  The remote-controlling instance opens a browser window and remembers the process ID or a reference to the new browser instance.

• Step 2

  The remote-controlling instance opens the page "remote_control.html" in the newly opened browser.

  You can call up the site through:

  inter.tlnplanner.nl/V9.3/remote/remote_control.html

   

  Permanently defined parameters must be passed to this page (see What parameters can I transfer?). The page uses JavaScript, does not need any user interaction and also has no outputs.

• Step 3

  If no TLNplanner internet instance is open yet, automatic login will occur without user interaction.

• Step 4

  After starting up, a check is run in TLNplanner internet to see whether a Remote Control request has been submitted. If a request is found, it is forwarded to the route planning use case. The stop-off points are added and a route is calculated (if applicable).

• Step 5

  The browser instance opened in step 1 can now be closed. Since there is no confirmation from TLNplanner internet to this browser, closing must be time-based. As soon as step 2 is finished, this means the site "remote_control.html" has loaded completely; the window can be closed again.

  Closing the window through JavaScript using "window.close()" is not possible, because the browser would always interrupt the user with a query.

  Note: Please note that data can only be transferred to Remote Control via a GET request (i.e. through a URL). A POST request is not possible.