warqueen 0.4.8

Simple message based networking, non-async and non-blocking
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
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89


## 0.4.8

### Fixed

- Upgraded dependencies to their latest versions.

## 0.4.7

### Fixed

- Disabled `rustls`'s `aws_lc_rs` feature, `ring` seems good enough for the scope of warqueen and `aws_lc_rs` depends on `aws-lc-sys` which seem to complicate the build process (that sometimes fail).

## 0.4.6

### Fixed

- Removed unnecessary unwraps on results from event sendings across channels that happens on listening tasks for converting streams into message events, for both sides (server and client).

### Added

- Added an optional thread count parameter to both client and server that will make the async runtime used for networking run on a threadpool of the given size if any. Default remains 1.
- Made specifying a socket address optional for server.
- Made specifying a desired port number optional for server.

## 0.4.5

### Fixed

- Connection lost errors that happen while reading a stream are now handled as a disconnection event instead of by a panic, for both sides (server and client).

## 0.4.4

### Fixed

- Connection time out is now handled as a disconnection event instead of by a panic, for both sides (server and client).

## 0.4.3

### Fixed

- Function `ClientNetworkingConnecting::new` may(?) now work across an actual network.

## 0.4.2

### Fixed

- Function `ServerListenerNetworking::new` now takes the server IP address too, so that it actually works on actual networks instead of being limited to localhost (I am *not* a networking person).

## 0.4.1

### Fixed

- Function `ServerListenerNetworking::new` used to panic (on an unwrap) when the `desired_port` is not available. Now it tries the next port, and the next, etc., until it finds an available port; as the doc already claimed it does.

## 0.4.0

Commit tagged [v0.4](https://github.com/anima-libera/warqueen/tree/v0.4).

### Added

- Type `SendingStateHandle` that can be used to know if a specific message is still in the process of being sent or is done already, and if it was successfully sent or why it failed. Messages that fail being sent no longer cause a panic.
- Client-side event `ClientEvent::FailedToConnect` that lets the client know when the connecting to the server gives up and fails, instead of never being notified.

## 0.3.0

Commit tagged [v0.3](https://github.com/anima-libera/warqueen/tree/v0.3).

### Added

- Type `ClonelessSending` that can be used in message types to allow senders to spare one clone of some data that is to be sent, only useful in a specific situation.
- A code example `both` that combines both the `client` and `server` code examples in one executable.
- A code example `cloneless` that builds on top of the `both` code example to demonstrate the use of `ClonelessSending`.
- This changelog ^^.

## 0.2.0

Commit tagged [v0.2](https://github.com/anima-libera/warqueen/tree/v0.2).

### Added

- Published v0.1.0 of sub-crate `warqueen_derive`, containing derive macros `NetSend` and `NetReceive` that implement the traits of the same name defined in `warqueen`.
- Re-exports of `warqueen_derive`'s two macros from `warqueen`.

## 0.1.0

Commit tagged [v0.1](https://github.com/anima-libera/warqueen/tree/v0.1).

First released version.