Timeline for Thread-safely transforming a value in a mutable map
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:02 | history | edited | URL Rewriter Bot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Aug 30, 2013 at 14:19 | audit | Reopen votes | |||
| Aug 30, 2013 at 14:23 | |||||
| Aug 26, 2013 at 9:34 | audit | Close votes | |||
| Aug 26, 2013 at 10:42 | |||||
| Aug 21, 2013 at 19:29 | audit | Reopen votes | |||
| Aug 21, 2013 at 19:29 | |||||
| Aug 9, 2013 at 18:21 | answer | added | Mushtaq Ahmed | timeline score: 2 | |
| Aug 9, 2013 at 17:15 | answer | added | Rex Kerr | timeline score: 2 | |
| Aug 9, 2013 at 15:48 | answer | added | Ionuț G. Stan | timeline score: 10 | |
| Aug 9, 2013 at 15:46 | answer | added | Régis Jean-Gilles | timeline score: 3 | |
| Aug 9, 2013 at 15:28 | comment | added | gourlaysama |
what about a single Akka actor that writes to the mutable map? Counter.add just sends a fire-and-forget message to it. As for reads, depending on your needs they can happen concurrently or go through the actor too.
|
|
| Aug 9, 2013 at 14:29 | history | asked | Travis Brown | CC BY-SA 3.0 |