Timeline for Class design for calling "the same method" on different classes from one place
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Sep 18, 2015 at 2:04 | history | suggested | Clinton Pierce | CC BY-SA 3.0 | Replaced link to popup heavy site |
| Sep 18, 2015 at 0:30 | review | Suggested edits | |||
| S Sep 18, 2015 at 2:04 | |||||
| Oct 31, 2013 at 20:09 | comment | added | betatester07 | yes, you are right, I will open new question. | |
| Oct 30, 2013 at 18:02 | comment | added | pdr | @betatester07: Not understanding your question, sorry. But it sounds unrelated to the original question, so I'd suggest raising it separately, rather than making this conversational. | |
| Oct 30, 2013 at 11:59 | comment | added | betatester07 | thanks. maybe, one more question - what is best approach to access other methods on one of my cache objects? | |
| Oct 30, 2013 at 11:54 | vote | accept | betatester07 | ||
| Oct 21, 2013 at 23:25 | comment | added | pdr | @betatester07: There shouldn't be a performance hit. If anything, it'll probably be slightly optimised by the framework. But feel free to profile it and be sure. | |
| Oct 21, 2013 at 21:01 | comment | added | betatester07 | observer pattern seems to me like the most elegant solution from the class design point of view, but our cache is not updated very often (mabye few times a week), how big is performance hit? | |
| Oct 21, 2013 at 14:31 | history | answered | pdr | CC BY-SA 3.0 |