Beginning of `stack-next` refactor
-Refactoring the protocol stack into something similar to a runtime. -Handles merging handler builders which is placing the ground work for plugins in. - Increased metadata generation during compilation enables less ser/de during execution. - Goal is to have an O(1) time from incoming operation to calling handlers. - Decreased penalty for using the statically typed API from within your code, now avoids some allocation. # Changes - Added `GiteratedRuntime` which is to replace the current unified stack - Added `RuntimeBuilder` which does what the current `OperationHandlers` struct does, but much better. - Added `RuntimeMetadata` to store type metadata for new `Any` based internals - Refactored serde_json out of the internal operation handling
parent: tbd commit: 708dea4
1 | use ; |
2 | |
3 | use ; |
4 | use Value; |
5 | |
6 | use crate GiteratedObject; |
7 | |
8 | |
9 | Send + Sync + Serialize + DeserializeOwned |
10 | |
11 | type Success: Serialize + DeserializeOwned + Send; |
12 | type Failure: Serialize + DeserializeOwned + Send; |
13 | |
14 | |
15 | |
16 | |
17 | |
18 | |
19 | |
20 | |
21 | |
22 | ; |
23 | |
24 | |
25 | type Success = Value; |
26 | |
27 | type Failure = Value; |
28 | |
29 | |
30 | |
31 | |
32 | |
33 | ; |
34 | |
35 | |
36 | type Success = ; |
37 | |
38 | type Failure = ; |
39 | |
40 | |
41 | /// The internal state of an operation, used to provide authentication information |
42 | /// and the ability to make giterated calls within handlers. |
43 | |
44 | ; |
45 |