Pieter Wuille 27f9ba23ef net: add V1Transport lock protecting receive state
Rather than relying on the caller to prevent concurrent calls to the
various receive-side functions of Transport, introduce a private m_cs_recv
inside the implementation to protect the lock state.

Of course, this does not remove the need for callers to synchronize calls
entirely, as it is a stateful object, and e.g. the order in which Receive(),
Complete(), and GetMessage() are called matters. It seems impossible to use
a Transport object in a meaningful way in a multi-threaded way without some
form of external synchronization, but it still feels safer to make the
transport object itself responsible for protecting its internal state.
2023-08-23 19:56:24 -04:00
..
2023-08-08 17:50:41 +02:00
2023-08-17 15:55:01 +02:00
2023-06-29 16:14:07 -06:00
2023-05-26 15:47:55 -07:00
2023-03-23 12:55:18 +01:00
2022-12-24 23:49:50 +00:00
2023-06-16 10:38:19 +01:00
2023-06-16 10:38:19 +01:00
2023-03-23 19:38:38 +01:00
2023-03-23 19:38:38 +01:00
2022-12-24 23:49:50 +00:00
2023-03-23 12:55:18 +01:00
2023-06-16 10:38:19 +01:00
2022-12-24 23:49:50 +00:00
2022-12-24 23:49:50 +00:00
2022-12-24 23:49:50 +00:00
2023-01-12 13:42:44 +00:00
2023-06-16 10:38:19 +01:00
2023-07-19 18:12:42 +02:00
2023-07-19 18:12:42 +02:00
2023-01-25 09:33:26 +01:00
2023-08-08 16:03:40 +02:00