Timeline for Observer pattern for unpredictable observation time
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 24, 2012 at 6:31 | vote | accept | JoJo | ||
| Jun 23, 2012 at 21:36 | comment | added | Giorgio | I honestly do not know if there is such a standard. But I do not think there is anything wrong for an object to generate an event when another object subscribes. | |
| Jun 23, 2012 at 21:00 | comment | added | JoJo | I don't know what the standard is. Is the standard to be notified of future events only or is it standard to be notified when someone subscribes late? | |
| Jun 23, 2012 at 20:11 | comment | added | Giorgio | Do you mean that with the standard observer pattern you only want to be notified about events that have occurred after subscription? | |
| Jun 23, 2012 at 18:36 | comment | added | JoJo | For the standard observer pattern, do programmers expect this behavior upon subscription? If not, then should I create two subscription functions - one just like your example, and another to only publish future events? | |
| Jun 23, 2012 at 8:15 | history | edited | Giorgio | CC BY-SA 3.0 |
added 154 characters in body
|
| Jun 23, 2012 at 8:10 | history | answered | Giorgio | CC BY-SA 3.0 |