template <>

class WireSyncClientImpl

Defined at line 888 of file fidling/gen/sdk/fidl/fuchsia.net.root/fuchsia.net.root/cpp/fidl/fuchsia.net.root/cpp/wire_messaging.h

Methods to make a sync FIDL call directly on an unowned handle or a

const reference to a |::fidl::ClientEnd

::fuchsia_net_root::RoutesV4>|,

avoiding setting up a client.

Public Methods

::fidl::OneWayStatus GlobalRouteSet (::fidl::ServerEnd< ::fuchsia_net_routes_admin::RouteSetV4> && route_set)

Returns a `RouteSetV4` containing all IPv4 routes from the global

routing table. Clients have unilateral access to add or remove routes

from the set. This includes the ability to remove routes installed by

the system, or routes installed by other clients of the `RouteSetV4`

protocol.

Note that the established connection to the `RouteSetV4` protocol will

have a few notable differences from a `RouteSetV4` obtained by

[`fuchsia.net.routes.admin/RouteTableV4.NewRouteSet`]:

- When removing a route from this route set, the route will be

completely removed from the system, including removal from all other

route sets to which it belongs.

- The protocol does not encode the lifetime of the route set or its

routes. Closing the client end will not cause the routes within this

route set to be removed from the system. Thus, routes added via this

route set will effectively be abandoned/unowned after this

client-end closes.

+ request `route set` grants access to the `RouteSetV4` protocol.

Allocates 40 bytes of message buffer on the stack. No heap allocation necessary.