Thanks,
Regarding asynchronous receive, what are the proms and cones between
Callback and using events?
In what context, _specifically_?
In general, there's little practical difference between using a callback
or an event. They are both essentially the same thing, except for some
minor semantic differences. That is, with an event, you always have to
use the add/remove methods, whereas with a callback you are generally
passing a delegate to a method (but it could be assigned to a property and
even added to/removed from the current value of a delegate property in a
similar fashion to the way an event works).
For specific APIs, there could sometimes be differences in the underlying
mechanics for a class that offers both, but in all the cases I'm aware of
it's simply a matter of what design choice the author of the class decided
on. Are you looking at some class that allows either subscription to an
event or providing a callback delegate according to the preference of the
client code?
Pete
