Timeline for What other patterns can I use for this singleton?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22, 2012 at 17:55 | vote | accept | ssube | ||
| Aug 22, 2012 at 15:03 | vote | accept | ssube | ||
| Aug 22, 2012 at 15:24 | |||||
| S Feb 18, 2012 at 0:30 | history | suggested | user34530 | CC BY-SA 3.0 | Fixed typos, grammar and formatting. |
| Feb 18, 2012 at 0:28 | review | Suggested edits | |||
| S Feb 18, 2012 at 0:30 | |||||
| Feb 16, 2012 at 23:54 | comment | added | ssube | I do think you're onto something with the tuple idea and 4, potentially with a global variable dictionary instead of a global parser. | |
| Feb 16, 2012 at 23:53 | comment | added | ssube | The log messages are formatted as-needed, so if the Logger can early-out based on severity level, the format will never occur, otherwise the format is triggered, then a brief lock for atomic write. What I do want is for all the log info from a single run of a single process to go into a single file, for a variety of reasons which include 6. Most logging only happens during error handling, at which point performance is tenth concern to in-order logging (stamped to the ms), making sure the log makes it to disk (the log is flushed if an error is logged), and so on. | |
| Feb 16, 2012 at 23:33 | comment | added | ssube | For 2, any plugin or most others bits of code may access the Server in order to create objects or load other plugins, but there must never be competing servers, hence the use of a singleton. I am well aware of all the implications of the (anti-)pattern, but that object is the ideal use case for it. For 3 , the Parser is also available to any plugin and at any time, but (4) it is Core-specific, so trying to move it there will likely help. For 5, the singleton creation and all calls are thread-safe (all the objects and their methods are, in fact)... | |
| Feb 16, 2012 at 21:45 | history | answered | Dipan Mehta | CC BY-SA 3.0 |