Timeline for Message bus in C#
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 15, 2020 at 10:41 | history | edited | Bohdan Yarema | CC BY-SA 4.0 |
added 1459 characters in body
|
| Feb 12, 2016 at 0:48 | comment | added | Jesse C. Slicer |
When it comes to overriding GetHashCode, you should have a reasonable guarantee of no collisions. I think yours could use a little help in that respect, and with that I give you Jon Skeet: stackoverflow.com/a/263416/3312
|
|
| Feb 8, 2016 at 8:10 | vote | accept | Bohdan Yarema | ||
| Feb 8, 2016 at 7:48 | history | edited | 200_success |
edited tags
|
|
| Feb 8, 2016 at 6:23 | answer | added | Heslacher | timeline score: 7 | |
| Feb 7, 2016 at 22:30 | history | tweeted | twitter.com/StackCodeReview/status/696461107737862148 | ||
| Feb 7, 2016 at 18:04 | comment | added | Bohdan Yarema | Well, I have them for situations like connection problems somewhere in program. So I can just send a message "Problem" and react with showing loading icon + "connection issues" text for user. That requires no arguments and that is a reason behind having non generic methods. | |
| Feb 7, 2016 at 17:59 | comment | added | RubberDuck | Why do you the non-generic versions of all these methods? | |
| Feb 7, 2016 at 17:57 | comment | added | Bohdan Yarema | @RubberDuck, cannot quite get what you are talking about, sorry. | |
| Feb 7, 2016 at 17:29 | comment | added | RubberDuck | Do you have a good reason to support weakly typed operations? I can only think of a handful of reasons to support it and most of them involve COM Interoperability. | |
| Feb 7, 2016 at 14:39 | history | edited | Quill | CC BY-SA 3.0 |
deleted 36 characters in body
|
| Feb 7, 2016 at 14:30 | review | First posts | |||
| Feb 7, 2016 at 14:49 | |||||
| Feb 7, 2016 at 14:28 | history | asked | Bohdan Yarema | CC BY-SA 3.0 |