Enum LauncherRequest

pub enum LauncherRequest {
    ExploreComponentOverPty {
        moniker: String,
        pty: ClientEnd<DeviceMarker>,
        tool_urls: Vec<String>,
        command: Option<String>,
        ns_layout: DashNamespaceLayout,
        responder: LauncherExploreComponentOverPtyResponder,
    },
    ExploreComponentOverSocket {
        moniker: String,
        socket: Socket,
        tool_urls: Vec<String>,
        command: Option<String>,
        ns_layout: DashNamespaceLayout,
        responder: LauncherExploreComponentOverSocketResponder,
    },
    ExplorePackageOverSocket {
        url: String,
        subpackages: Vec<String>,
        socket: Socket,
        tool_urls: Vec<String>,
        command: Option<String>,
        responder: LauncherExplorePackageOverSocketResponder,
    },
    ExplorePackageOverSocket2 {
        fuchsia_pkg_resolver: FuchsiaPkgResolver,
        url: String,
        subpackages: Vec<String>,
        socket: Socket,
        tool_urls: Vec<String>,
        command: Option<String>,
        responder: LauncherExplorePackageOverSocket2Responder,
    },
}

Variants

ExploreComponentOverPty

Launch a dash process scoped to the component with the given moniker, forwarding the given stdio PTY.

Fields

moniker: String

pty: ClientEnd<DeviceMarker>

tool_urls: Vec<String>

command: Option<String>

ns_layout: DashNamespaceLayout

responder: LauncherExploreComponentOverPtyResponder

ExploreComponentOverSocket

Launch a dash process scoped to the component with the given moniker, forwarding the given stdio socket.

The dash launcher will implicitly create a PTY and transfer bytes between the PTY and the socket.

Fields

moniker: String

socket: Socket

tool_urls: Vec<String>

command: Option<String>

ns_layout: DashNamespaceLayout

responder: LauncherExploreComponentOverSocketResponder

ExplorePackageOverSocket

Launch a dash process with the indicated [sub]package loaded into the namespace at /pkg, forwarding the given stdio socket.

The dash launcher will implicitly create a PTY and transfer bytes between the PTY and the socket.

Always uses [fuchsia.dash/FuchsiaPkgResolver.FULL] to resolve package URLs with scheme “fuchsia-pkg”. Use [fuchsia.dash/Launcher.ExplorePackageOverSocket2] instead to pick which resolver to use with “fuchsia-pkg” URLs.

Fields

url: String

subpackages: Vec<String>

socket: Socket

tool_urls: Vec<String>

command: Option<String>

responder: LauncherExplorePackageOverSocketResponder

ExplorePackageOverSocket2

Launch a dash process with the indicated [sub]package loaded into the namespace at /pkg, forwarding the given stdio socket.

The dash launcher will implicitly create a PTY and transfer bytes between the PTY and the socket.

Fields

fuchsia_pkg_resolver: FuchsiaPkgResolver

url: String

subpackages: Vec<String>

socket: Socket

tool_urls: Vec<String>

command: Option<String>

responder: LauncherExplorePackageOverSocket2Responder

Implementations

impl LauncherRequest

pub fn into_explore_component_over_pty( self, ) -> Option<(String, ClientEnd<DeviceMarker>, Vec<String>, Option<String>, DashNamespaceLayout, LauncherExploreComponentOverPtyResponder)>

pub fn into_explore_component_over_socket( self, ) -> Option<(String, Socket, Vec<String>, Option<String>, DashNamespaceLayout, LauncherExploreComponentOverSocketResponder)>

pub fn into_explore_package_over_socket( self, ) -> Option<(String, Vec<String>, Socket, Vec<String>, Option<String>, LauncherExplorePackageOverSocketResponder)>

pub fn into_explore_package_over_socket2( self, ) -> Option<(FuchsiaPkgResolver, String, Vec<String>, Socket, Vec<String>, Option<String>, LauncherExplorePackageOverSocket2Responder)>

pub fn method_name(&self) -> &'static str

Name of the method defined in FIDL

Trait Implementations

impl Debug for LauncherRequest

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.