-
I was attempting to return nice error responses for certain errors. For example i'd like to return a 408 when a timeout occurs. However it seems to also close the socket.
While testing this out I ran…
-
earlier this year I created an asr, and built a test client, connect, transcribe, send audiochunks from 2 wav files,
check tanscript..
all good
trying to build my own service runner
testing ea…
-
I came across this project while troubleshooting some issues with the "bwalink" docker container and figured this might be a more seamless integration.
I'm running into issues adding the spa connec…
-
```toml
hyper = { version = "=1.5.1", features = ["client", "http1"] }
hyper-util = { version = "=0.1.10", features = ["http1", "tokio", "server"] }
```
```text
MacBook Pro 16-inch, 2019
2.4 G…
-
#### Problem Overview
I'm implementing a communication layer in Rust that supports both TCP and QUIC protocols for data exchange between a client and a server. I'm using **Quinn** for the QUIC implem…
-
### Description
Initial targeted list of examples in this [pad](https://pad.riot-os.org/aPbbp77KTEKZb--l6GwdUA?both).
For each example,
- [ ] minimize
- [ ] check name
- [ ] no embassy
…
-
I took the very basic server example and changed the protocol from `opc.tcp` to `opc.http`. I want to deploy the server to heroku but that apparently does not support tcp endpoints and requires http/s…
-
1. Create an SSL server using the example in https://orthecreedence.github.io/cl-async/tcp-ssl
```lisp
(tcp-ssl-server "127.0.0.1" 443
(lambda (socket data)
(form…
naryl updated
3 weeks ago
-
Websocat4 is a full rewrite of Websocat1. It makes it impractical to implement all the features accumulated in Websocat1 at the same time.
This issue tracks status of porting Websocat1 features to …
-
I am trying to implement a basic server push scenario where the server makes multiple push requests. The client is first expected to process pushed requests and only then await for the main response. …