pub enum RequestOrigin {
Inbound,
Outbound,
}Expand description
Which side issued a request.
Both directions go through one table because both need the same three things: uniqueness of the id, a cancellation handle, and a deadline. A server that samples from a client has exactly the bookkeeping a server has when a client calls a tool, and two tables would be two places for one rule to be wrong in.
Variants§
Trait Implementations§
Source§impl Clone for RequestOrigin
impl Clone for RequestOrigin
impl Copy for RequestOrigin
Source§impl Debug for RequestOrigin
impl Debug for RequestOrigin
impl Eq for RequestOrigin
Source§impl Hash for RequestOrigin
impl Hash for RequestOrigin
Source§impl PartialEq for RequestOrigin
impl PartialEq for RequestOrigin
impl StructuralPartialEq for RequestOrigin
Auto Trait Implementations§
impl Freeze for RequestOrigin
impl RefUnwindSafe for RequestOrigin
impl Send for RequestOrigin
impl Sync for RequestOrigin
impl Unpin for RequestOrigin
impl UnsafeUnpin for RequestOrigin
impl UnwindSafe for RequestOrigin
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Mutably borrows from an owned value. Read more