Home
last modified time | relevance | path

Searched hist:b8a716965a5647b9e991cfbaac4538446ac7f00e (Results 1 – 2 of 2) sorted by relevance

/haiku/headers/private/net/
H A DSocketMessenger.hb8a716965a5647b9e991cfbaac4538446ac7f00e Sun May 15 01:22:26 UTC 2016 Rene Gollent <rene@gollent.com> BSocketMessenger: Further improvements.

- Messages that expect a reply are now tagged with a unique ID field to
indicate that expectation to the receiving socket messenger.
- The messenger now maintains a map of received reply IDs and their
corresponding messages, along with a message queue of other unsolicited
replies.
- After successfully connecting, the messenger now spawns a thread
whose sole responsibility is receiving and parsing all incoming messages,
and consequently sorting them into the aforementioned data structures based
on the presence of the reply ID. Callers who are awaiting either replies or
other messages are signalled appropriately via a semaphore. This allows
multiplexing of both types of messages on the same socket.
/haiku/src/kits/network/libnetapi/
H A DSocketMessenger.cppb8a716965a5647b9e991cfbaac4538446ac7f00e Sun May 15 01:22:26 UTC 2016 Rene Gollent <rene@gollent.com> BSocketMessenger: Further improvements.

- Messages that expect a reply are now tagged with a unique ID field to
indicate that expectation to the receiving socket messenger.
- The messenger now maintains a map of received reply IDs and their
corresponding messages, along with a message queue of other unsolicited
replies.
- After successfully connecting, the messenger now spawns a thread
whose sole responsibility is receiving and parsing all incoming messages,
and consequently sorting them into the aforementioned data structures based
on the presence of the reply ID. Callers who are awaiting either replies or
other messages are signalled appropriately via a semaphore. This allows
multiplexing of both types of messages on the same socket.