mirror of
https://github.com/RetroShare/RetroShare.git
synced 2024-10-01 02:35:48 -04:00
Better documentation about multimap usage
This commit is contained in:
parent
2b1c9b74d1
commit
f19fe56a93
@ -172,8 +172,12 @@ private:
|
|||||||
|
|
||||||
/**
|
/**
|
||||||
* @brief Ingoing mail and receipt processing queue.
|
* @brief Ingoing mail and receipt processing queue.
|
||||||
* Items are saved in config and then deleted in destructor for consistence
|
* At shutdown remaining items are saved in config and then deleted in
|
||||||
* accross RetroShare shutdowns.
|
* destructor for consistence accross RetroShare instances.
|
||||||
|
* In order to avoid malicious messages ( non malicious collision has 1/2^64
|
||||||
|
* probablity ) to smash items in the queue thus causing previous incoming
|
||||||
|
* item to not being processed and memleaked multimap is used instead of map
|
||||||
|
* for incoming queue.
|
||||||
*/
|
*/
|
||||||
typedef std::unordered_multimap<RsGxsMailId, RsGxsMailBaseItem*> inMap;
|
typedef std::unordered_multimap<RsGxsMailId, RsGxsMailBaseItem*> inMap;
|
||||||
inMap ingoingQueue;
|
inMap ingoingQueue;
|
||||||
|
Loading…
Reference in New Issue
Block a user