Changes between Version 3 and Version 4 of Ticket #10953, comment 6


Ignore:
Timestamp:
Jul 27, 2014, 9:36:10 PM (10 years ago)
Author:
ttcoder

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #10953, comment 6

    v3 v4  
    2424- it's possible the 'RemoteHWInterface' screen is invoked through an incoming sshd connection being forwarded to the app_server(?). I don't understand how/when the 'HTML5HWInterface' is supposed to be instantiated, and couldn't make it occur here.
    2525- it seems applications tell app_server what "screen" they want to be displayed on [http://grok.bikemonkey.org/source/xref/haiku/src/kits/app/AppMisc.cpp#210 here], passing $TARGET_SCREEN to app_server: since they are run from the same Terminal session that was opened by the initial connection, and sub-processes/apps inherit the environment variables of their parent Terminal, all apps launched from there will be displayed on the remote desktop/screen instead of the main screen.
     26
     27So the server-side sequence looks like this:
     28- sshd executes the "TARGET_SCREEN=localhost:10900; Terminal" ... line
     29- Terminal launches, going through [http://grok.bikemonkey.org/source/xref/haiku/src/kits/app/Application.cpp#1348 BApplication::_ConnectToServer()]
     30- create_desktop_connection() [http://grok.bikemonkey.org/source/xref/haiku/src/kits/app/AppMisc.cpp#210 sends] the target screen to app_server
     31- app_server opens port 10900 (by instantiating class RemoteHWInterface)
     32- ..etc
     33
     34