Dittoing remote QNX Photon sessions
The normal mode of using Phindows (without the -n option) causes a private session of Photon to be started on the QNX machine you've connected to.
Connecting to a remote Photon session
Suppose you need to look at a Photon application running on some QNX machine other than the one with the modem you're connecting
to. Not a problem. You can use the -n option to specify the full QNX pathname of any Photon session on that remote QNX network.
Starting Photon sessions on other QNX nodes
Suppose the QNX machine you log into has lots of modems, but not a lot of spare CPU or memory. You want to start up a private
Photon session and discover that node 2 has lots of spare resources (in QNX, any node will do).
Spanning a single Photon session across multiple screens
You can use both Phindows and phditto (which comes standard with Photon) to stretch a single Photon space across multiple desktops. Some (or all) of these desktops
can be QNX computers, some (or all) of these desktops can be Windows desktops, and some (or all) can be X workstations as
well.
Sharing a Photon session (workgroup computing)
The normal mode of Dittoing someone else's Photon session (specifying -n) is to have a single cursor that can be controlled by either the local or remote user. Similarly, keystrokes from either
keyboard can be entered into the application with keyboard focus, which is normally what you want for a remote training or
debugging session.
Enabling offscreen context support
The normal mode of Dittoing someone else's Photon session (specifying -n) is to have a single cursor that can be controlled by either the local or remote user. Similarly, keystrokes from either
keyboard can be entered into the application with keyboard focus, which is normally what you want for a remote training
or debugging session.
Using predefined Photon services
The -s command-line option simplifies the task of creating shortcuts to Photon applications within the Windows desktop.