Google is committed to advancing racial equity for Black communities. See how.

Implement a FIDL client

Prerequisites

This tutorial builds on the FIDL server tutorial. For the full set of FIDL tutorials, refer to the overview.

Overview

This tutorial implements a client for a FIDL protocol and runs it against the server created in the previous tutorial. The client in this tutorial is synchronous. There is an alternate tutorial for asynchronous clients.

If you want to write the code yourself, delete the following directories:

rm -r examples/fidl/hlcpp/client_sync/*

Create a stub component

  1. Set up a hello world component in examples/fidl/hlcpp/client. You can name the component echo-client, and give the package a name of echo-hlcpp-client-sync.

  2. Once you have created your component, ensure that the following works:

    fx set core.x64 --with //examples/fidl/rust/client
    
  3. Build the Fuchsia image:

    fx build
    
  4. In a separate terminal, run:

    fx serve
    
  5. In a separate terminal, run:

    fx shell run fuchsia-pkg://fuchsia.com/echo-hlcpp-client-sync#meta/echo-client.cmx
    

Edit GN dependencies

  1. Add the following dependencies:

      deps = [
        "//examples/fidl/fuchsia.examples",
        "//sdk/lib/sys/cpp",
      ]
    
    
  2. Then, include them in main.cc:

    #include <fuchsia/examples/cpp/fidl.h>
    #include <lib/async-loop/cpp/loop.h>
    #include <lib/async-loop/default.h>
    #include <lib/sys/cpp/component_context.h>
    

    The reason for including these dependencies is explained in the server tutorial.

Edit component manifest

  1. Include the Echo protocol in the client component's sandbox by editing the component manifest in client.cmx.

    {
        "program": {
            "binary": "bin/fidl_echo_hlcpp_client"
        },
        "sandbox": {
            "services": [
                "fuchsia.examples.Echo"
            ]
        }
    }
    
    

Connect to the server

This section adds code the main() function that connects to the server and makes requests to it.

Initialize a proxy class

The code then creates a proxy class for the Echo protocol, and connects it to the server. In the context of FIDL, proxy designates the code generated by the FIDL bindings that enables users to make remote procedure calls to the server. In HLCPP, the proxy takes the form of a class with methods corresponding to each FIDL protocol method.

int main(int argc, const char** argv) {
  fuchsia::examples::EchoSyncPtr echo_proxy;
  auto context = sys::ComponentContext::Create();
  context->svc()->Connect(echo_proxy.NewRequest());

  ZX_ASSERT(echo_proxy->SendString("hi") == ZX_OK);
  std::string response;
  ZX_ASSERT(echo_proxy->EchoString("hello", &response) == ZX_OK);
  printf("Got response: %s\n", response.c_str());

  // TODO(fcz): this currently does not pass on CQ
  // return response == "hello" ? 0 : 1;
  return 0;
}
  • fuchsia::examples::EchoSyncPtr is an alias for fidl::SynchronousInterfaceRequest<fuchsia::examples::Echo> generated by the bindings. This class will proxy requests for the Echo protocol over the channel that it is bound to.
  • The code calls EchoSyncPtr::NewRequest(), which will create a channel, bind the class to one end, and return the other end
  • The returned end is passed to sys::ServiceDirectory::Connect().
    • Analogous to the call to context->out()->AddPublicService() on the server side, Connect has an implicit second parameter here which is the protocol name ("fuchsia.examples.Echo"). This is where the input to the handler defined in the previous tutorial comes from: the client passes it in to Connect, which then passes it to the handler.

An important point to note here is that this code assumes that /svc already contains an instance of the Echo protocol. This is not the case by default because of the sandboxing provided by the component framework.

Send requests to the server

The code makes two requests to the server:

  • An EchoString request
  • A SendString request
int main(int argc, const char** argv) {
  fuchsia::examples::EchoSyncPtr echo_proxy;
  auto context = sys::ComponentContext::Create();
  context->svc()->Connect(echo_proxy.NewRequest());

  ZX_ASSERT(echo_proxy->SendString("hi") == ZX_OK);
  std::string response;
  ZX_ASSERT(echo_proxy->EchoString("hello", &response) == ZX_OK);
  printf("Got response: %s\n", response.c_str());

  // TODO(fcz): this currently does not pass on CQ
  // return response == "hello" ? 0 : 1;
  return 0;
}

For EchoString the code passes in a pointer for each response parameter (in this case, the EchoString method only has one response parameter), which is written with the response from the server, whereas this does not apply to SendString since it is a [fire and forget method][one-way]. The call to EchoString will block until it receives a message from the server. Both methods will return a zx_status_t indicating the result of the method call.

Though the server implementation sends an OnString event in response to the SendString request, the sync bindings do not provide a way to handle this event.

Run the client

If you try running the client directly, you'll notice that the error handler gets called because the client does not automatically get the Echo protocol provided in its sandbox (in /svc). In order to get this to work, a launcher tool is provided that launches the server, creates a new Environment for the client that provides the server's protocol, then launches the client in it.

  1. Configure your GN build:

    fx set core.x64 --with //examples/fidl/hlcpp/server --with
    //examples/fidl/hlcpp/client_sync --with //examples/fidl/test:echo-launcher
    
  2. Build the Fuchsia image:

    fx build
    
  3. Run the launcher by passing it the client URL, the server URL, and the protocol that the server provides to the client:

    fx shell run fuchsia-pkg://fuchsia.com/echo-launcher#meta/launcher.cmx fuchsia-pkg://fuchsia.com/echo-hlcpp-client-sync#meta/echo-client.cmx fuchsia-pkg://fuchsia.com/echo-hlcpp-server#meta/echo-server.cmx fuchsia.examples.Echo
    

You should see the client print output in the QEMU console (or using fx log).

[117942.207] 757245:757247> Running echo server
[117942.223] 757349:757352> Got response: hello