Hybrid behavior = mix of Standard and Launcher behaviors.
Theoption supports both the Java plug-in and the Reflection for the Web Launcher. The user’s setup determines how the Reflection for the Web sessions are launched, and what the user experiences.
The Hybrid “Standard” experience:
When the user has the Java browser plug-in enabled (in Internet Explorer 11), sessions are launched as they were in previous versions of Reflection for the Web.
The user sees the embedded links list, where they can click a session to launch in a separate window (legacy behavior).
The browser dependency keeps the browser open after the session is launched.
The Hybrid “Launcher” experience:
Be sure to note the Browser-specific behaviors. The user exerience varies according to the browser being used.
The user also sees the newbutton, which requires Web Start (JNLP).
Note: The default Display Links List button can be renamed.
If this user has Reflection for the Web Launcher installed on the workstation, they could launch their links list and their terminal sessions by clicking .
If the Administrator enabled individual downloads, users will see a link to Download and Install the Reflection for the Web Launcher, RWebLauncher.msi.
A user who has the Reflection for the Web Launcher installed on their workstation — and does not have the Java plug-in — sees only the button. Sessions are launched using Web Start (JNLP) instead of the Java browser plug-in.
When clicked, thelaunches the familiar links list.
When a session is clicked, or if a direct URL is provided, the session opens in a separate window.
After a Reflection for the Web session is launched via the Reflection for the Web Launcher, the browser can be closed (no dependency).