template <>class WireWeakSyncClientImpl
Defined at line 5356 of file fidling/gen/sdk/fidl/fuchsia.bluetooth.bredr/fuchsia.bluetooth.bredr/cpp/fidl/fuchsia.bluetooth.bredr/cpp/wire_messaging.h
Public Methods
::fidl::WireResult< ::fuchsia_bluetooth_bredr::Profile::Advertise> Advertise (::fuchsia_bluetooth_bredr::wire::ProfileAdvertiseRequest ProfileAdvertiseRequest)Register a set of services.
These services will be discoverable via Service Discovery Protocol server.
All services advertising the same channel must be added at once - if services are already
registered on any channel advertised, registration will fail, the receiver will be closed
with ZX_ERR_ALREADY_BOUND and an error will be returned.
The ConnectionReceiver will get calls for connections to the channels included in the
`protocol_descriptor` or `alternative_protocol_descriptors` in the services advertised.
The receiver will be closed if there are any errors advertising.
The `ConnectionReceiver::OnRevoke` event can be used to synchronize revoking the
advertisement, if necessary. Closing the `ConnectionReceiver` protocol will also stop
advertising these services.
If the advertisement cannot be made for any reason, an error of `INVALID_ARGUMENTS`
will be returned and the receiver will be closed with a suitable epitaph.
Returns the set of services that are registered via the Service Discovery Protocol
server. The returned services may differ from the input `services` if any L2CAP protocol
descriptors request `PSM_DYNAMIC`. In this case, the `Profile` server shall assign a valid
PSM and include this value in the returned services.
Request is heap-allocated. Response is heap-allocated.
::fidl::WireResult< ::fuchsia_bluetooth_bredr::Profile::Connect> Connect (const ::fuchsia_bluetooth::wire::PeerId & peer_id, ::fuchsia_bluetooth_bredr::wire::ConnectParameters connection)Connect an L2CAP or RFCOMM channel to the connected peer identified by `peer_id` using the
desired `connection` parameters listed. Dynamic PSMs can be specified in `connection`.
Returns the channel connected once established, or an error code if the channel could not
be connected.
Allocates 160 bytes of request buffer on the stack. Response is heap-allocated.