pass_ball
| Crates.io | pass_ball |
| lib.rs | pass_ball |
| version | 0.1.5 |
| source | src |
| created_at | 2020-07-16 09:22:58.41309 |
| updated_at | 2020-10-21 03:30:29.517534 |
| description | mssage queue written by rust. |
| homepage | https://github.com/wangmarkqi/pass_ball.git |
| repository | https://github.com/wangmarkqi/pass_ball.git |
| max_upload_size | |
| id | 265700 |
| size | 78,041 |
Wang Qi (wangmarkqi)
documentation
https://github.com/wangmarkqi/pass_ball.git
README
Pass_ball
Pass_ball is message queue written by rust. Pass_ball has two mode to use,one is traditional sub-pub,another is req-resp like http server. The features of pass include:
-
No client: All functions are realised by http api, see python requests example in test directory.
-
No size limit: Pass can be use to send file between devices with no fixed ip.
-
Req-resp mode: In this mode ,Pass will feels like a synchronise http server. This request-response mode is useful among iot devices with no fix ip.
-
Persisitent data by config: Pass will clean data beyond time scope specified by sub-conf api. Therefore messages to subscriber might be duplicate.
-
User flexibility: it is the duty of end users to delete useful topics.
Quich Start
See test directory for guidance.
- pub-sub mode:
- cargo run main.rs
- python pub.py
- python sub.py
- req-resp mode:
- cargo run main.rs
- python req.py
- python resp.py(should run fast enough in time scope)
.env Conf Example
URL=127.0.0.1:8884
ROOT=D://myrust/pass
SLEDDIR=${ROOT}/data/db