Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with mediator
Search options answers only
not deleted
user 9381
The mediator pattern defines an object that encapsulates how a set of objects interact.
0
votes
Use of mediator design pattern with mailing list implementation
I'm not familiar with mediator pattern, but I see it like a hub. From Wikipedia:
The essence of the Mediator Pattern is to "Define an object that encapsulates how a set of objects interact". …
- 285
2
votes
Use of mediator design pattern with mailing list implementation
login is a setter method and should be named setLogin, or even better, only used in the constructor to make subclasses of MailUser immutable
- 285