Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Difference From ump-0.11.0 To ump-0.12.0
2023-08-31
| ||
14:34 | Document ReplyContext. check-in: 61295fc1c3 user: jan tags: trunk | |
2023-08-14
| ||
23:03 | Release maintenance. check-in: b08bb813bf user: jan tags: trunk, ump-0.12.0 | |
22:55 | Update swctx to 0.2.1. check-in: 3eaac7ef46 user: jan tags: trunk | |
2023-07-29
| ||
02:10 | Make a note about project status. check-in: eb09b3724b user: jan tags: trunk | |
2023-07-28
| ||
22:19 | Release maintenance. check-in: bfeac614fd user: jan tags: trunk, ump-0.11.0 | |
22:11 | Return the correct Error type from ReplyContext methods. Documentation updates. check-in: 8ef3a429d7 user: jan tags: trunk | |
Changes to .efiles.
1 2 3 4 5 6 7 8 9 | 1 2 3 4 5 6 7 8 9 10 11 12 | - - - | Cargo.toml README.md www/index.md www/changelog.md src/err.rs src/lib.rs src/server.rs src/client.rs src/rctx.rs |
Changes to Cargo.toml.
1 2 | 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 | - + - - + - + - - + + + - + + + + | [package] name = "ump" |
Changes to src/client.rs.
| 1 2 3 4 5 6 7 8 | - + |
|
︙ | |||
49 50 51 52 53 54 55 | 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 90 91 92 93 94 | - + - + - - - + + - + - + - - + - | // Create a per-call reply context. // This context could be created when the Client object is being created // and stored in the context, and thus be reused for reach client call. // One side-effect is that some of the state semantics becomes more // complicated. // The central repo has such an implementation checked in, but it seems to // have some more corner cases that aren't properly handled. |
︙ |
Changes to src/err.rs.
1 2 3 4 5 6 7 8 | 1 2 3 4 5 6 7 8 9 10 | + + | use std::fmt; use crate::rctx::RCtxState; /// Module-specific error codes. #[derive(Debug)] pub enum Error<E> { /// The server object has shut down. /// /// Happens when clients: |
︙ | |||
48 49 50 51 52 53 54 | 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 | - - - - - - - - - - + + + + + + + + + + + + | _ => panic!("Not an Error::App") } } } impl<E: fmt::Debug> std::error::Error for Error<E> {} |
Changes to src/rctx.rs.
1 2 3 4 5 6 7 | 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 90 91 92 93 94 | - - - - + + + + + + + + + + + + + + + - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + | //! Allow a thread/task, crossing sync/async boundaries in either direction, to //! deliver an expected piece of data to another thread/task, with //! notification. //! //! These are simple channels used to deliver data from one endpoint to //! another, where the receiver will block until data has been delivered. |
Deleted src/rctx/err.rs.
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
|
Deleted src/rctx/inner.rs.
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
|
Deleted src/rctx/public.rs.
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
|
Changes to src/server.rs.
| 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | - + - - + + + - + |
|
︙ |
Changes to www/changelog.md.
1 2 3 4 5 6 7 8 9 10 11 12 | 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 | + + + + + + + - - + + + + | # Change Log ## [Unreleased] ### Added ### Changed ### Removed ## [0.12.0] - 2023-08-15 ### Changed - Include tests when publishing crate. - Bugfix: Use `err::Error` rather than `rctx::err::Error` in rctx::public, giving `ReplyContext::reply()` and `ReplyContext::fail()` the correct return types. |
︙ | |||
31 32 33 34 35 36 37 | 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 | - + | - Add `send()`/`asend()` wrappers around the new `req()`/`areq()` methods with a deprecation notice. - Add a `dev-docs` feature to allow internal documentation notes to be included in generated documentation. ### Changed |
︙ |
Changes to www/index.md.
1 2 3 4 5 6 7 8 9 10 11 12 13 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 | + + + + + + | # Micro-Message Passing Library The _ump_ crate is a simple client/server message passing library for intra-process communication. Its primary purpose is to allow cross async/non-async communication (for both the server and client endpoints). ## Change log The details of changes can always be found in the timeline, but for a high-level view of changes between released versions there's a manually maintained [Change Log](./changelog.md). ## Project Status _ump_ is in _maintenance mode_; it is feature-complete, but will receive bugfixes and improvements to implementation/documentation. |