b8a716965a
- 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. |
||
---|---|---|
.. | ||
AddressUtilities.h | ||
arp_control.h | ||
bosii_driver.h | ||
dns_resolver.h | ||
DynamicBuffer.h | ||
ether_driver.h | ||
ethernet.h | ||
HttpTime.h | ||
net_buffer.h | ||
net_datalink_protocol.h | ||
net_datalink.h | ||
net_device.h | ||
net_notifications.h | ||
net_protocol.h | ||
net_routing_info.h | ||
net_socket.h | ||
net_stack_interface.h | ||
net_stack.h | ||
net_stat.h | ||
NetBufferUtilities.h | ||
NetServer.h | ||
NetUtilities.h | ||
ProtocolUtilities.h | ||
r5_compatibility.h | ||
SocketMessenger.h | ||
userland_ipc.h | ||
WPASupplicant.h |