Thomas Eizinger 355726db7a refactor(connlib): clarify design of p2p control protocol (#6980) ...

This incorporates the feedback from #6939 after a discussion with
@conectado. We agreed that the protocol should be more event-based,
where each message has its own event type. Events MAY appear in pairs or
other cardinality combinations, meaning semantically they could be seen
as requests and responses. In general though, due to the unreliable
nature of IP, it is better to view them as events. Events are typically
designed to be idempotent which is important to make this protocol work.
Using events also means it is not as easy to fall into the "trap" of
modelling requests / responses on the control protocol level.

2024-10-09 00:45:30 +00:00

..

proptest-regressions

chore(connlib): implement IP translation according to RFC6145 (#5364)

2024-06-14 21:33:07 +00:00

src

refactor(connlib): clarify design of p2p control protocol (#6980)

2024-10-09 00:45:30 +00:00

Cargo.toml

refactor(connlib): remove pnet_packet (#6659)

2024-09-11 23:52:48 +00:00