gmt_dos-clients_scope 3.1.1

GMT DOS Scope Client
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

# Examples

## Scope

All examples are using data from the same server, that is run with
```text
RUST_LOG=info cargo run --features server --example tx
```

### async

Asynchronous scope using [tokio](https://tokio.rs/) runtime:

```text
RUST_LOG=info cargo run --features client --example async
```

### async-macro

Same as `async` but defining the scope with a procedural function macro:

```text
RUST_LOG=info cargo run --example async-macro
```

![scope example](txrx.png)

## Shot

### Server

```text
RUST_LOG=info cargo run --release --example sinsin --features server --no-default-features
```

### Client

```text
RUST_LOG=info cargo run --release --example async_shot
```

![shot example](sinsin.png)


## NICE-DCV

If [NICE-DCV](https://aws.amazon.com/hpc/dcv/) is installed on the remote server, the client can be run on the server as well.

First check if the DCV server is up and running:
```shell
sudo systemctl status dcvserver.service
```
then if some DCV sessions are already set
```shell
dcv list-sessions
```
and if not, create a new session:
```shell
dcv create-session --storage-root %home% 1
```