Read the statement by Michael Teeuw here.
Screencast on all clients
-
@skhynix I’m not sure I understand
the module has a node_helper, so it needs a server side. full or serveronly for the client side of the module to workclient only would be a client side to the server only.
does a chrome browser on the client side pi, connecting to the server, work to present the cast window?
-
@sdetweil The client does not present a cast window in clientonly or browser mode.
-
@skhynix sorry, still don’t understand
server only has no UI
how/where are you viewing that does open a screen cast window
what server is the client only connecting to?
-
@sdetweil When I cast, my pi4b opens a cast window on the server even in serveronly mode. the server is running the latest raspbian os with GUI. Aside from casting, the serveronly instance does not show any MM2 UI.
The clientonly device is a pi400, also running the latest raspbian os. The only difference between the client and server is that the clientonly does not have any of the modules or config files set up. Those are all run from the server. -
@skhynix so it would appear that the cast is a process started by the node_helper, and it can only run where the node_helper is running.
confirmed by looking at the code
-
@sdetweil Do you know if there’s a way to run the node_helper on the client device?
Something like a semi-independent client that uses a config from a serveronly device while additionally running part of it’s own? -
@skhynix no. node _helpers only run on the server side. and this module is designed to open it’s cast window on the machine acting as server, via it’s node_helper (thus the ‘helper’ part of it’s name)
and it assumes the client is there as well.
