ruststream 0.7.5

Async messaging framework for Rust: broker-agnostic traits, router, codecs, and a conformance harness for broker authors.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

---
sidebar_position: 1
title: broker
description: "TestApp::broker addresses one broker of the app by its production type, for publishing to it and reading its records."
---

import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

# broker

[`TestApp::broker`](api:ruststream::testing::TestApp::broker) addresses one broker of the app by its production type, for publishing to it and reading its records.

`B` is the type the app registered, so `MemoryBroker` and `MemoryBroker<Retaining>` are two different brokers.
The [`BrokerHandle`](api:ruststream::testing::BrokerHandle) it returns publishes onto that broker with [`message(&v)`](./message.md) and opens its records: [`subscriber(name)`](../records/subscriber.md) and [`published::<T>(name)`](../records/published.md).
A subscription name is local to its broker: the `"orders"` of one broker is not the `"orders"` of the other.
`broker` panics when the app has no broker of type `B` or more than one; two brokers of one type are addressed by label with [`broker_named`](./broker-named.md).
In live mode the test's input reaches the broker through its connected form's default publish policy.

## Example

<Tabs groupId="api">
<TabItem value="macros" label="Macros">

```rust reference="examples/testing_driving.rs#broker"
```

</TabItem>
<TabItem value="manual" label="Manual">

```rust reference="examples/manual/testing_driving.rs#broker"
```

</TabItem>
</Tabs>