Is there a design pattern that deals with callback mechanism?

Question

Is there a design pattern that deals with callback mechanism?

Answer 1

That would be the Observer Pattern - From Wikipedia

The observer pattern (a subset of the asynchronous publish/subscribe pattern) is a software design pattern in which an object, called the subject, maintains a list of its dependents, called observers, and notifies them automatically of any state changes, usually by calling one of their methods. It is mainly used to implement distributed event handling systems.

Answer 2

callback is a form strategy design pattern

Answer 3

Severals:

check http://people.bu.edu/azs/teaching/cs108/2006fall/callback_pattern.pdf

and:

Visitor Pattern: http://en.wikipedia.org/wiki/Visitor_pattern

Observer pattern : http://en.wikipedia.org/wiki/Observer_pattern

Strategy Pattern : http://en.wikipedia.org/wiki/Strategy_pattern

what prgramming language, what do you want to do exactly?

Answer 4

The Observer Pattern comes to mind.

One object (suscriber) can suscribe to another object (publisher). When the publisher changes or is updated, he can notify all his suscribers.

Depending on what language you are using, you can specify a function that should be called on notifies.

*http://en.wikipedia.org/wiki/Observer_pattern*

It is well described in Design Patterns: Elements of Reusable Object-Oriented Software [Gang of Four]

Answer 5

External polymorphism - An object has a reference to a another object and a function to call on that object. It can be viewed as a single type, thus you can mix and match objects and functions to call for the event. Delegates are an example of this pattern. This is more of a C# style approach.

Observer pattern - You use an interface/base class that an object can implement and register this interface to an event. More of a Java style approach.

Check the answer I posted here for a C++ solution for delegates/external polymorphism: http://stackoverflow.com/questions/516411/raw-function-pointer-from-a-bound-method/516537#516537

Answer 6

It depends on how the callback is used.

Design patterns are all about communicating your intent.

If you intended to allow one or more callbacks to be registered and they can be called as notification "at some point in the future", you're talking Observer. Also -- the actual invocation of the callback in this case is usually "optional" or triggered based on some stimulus. (The callbacks may or may not ever be called)

If you intended to pass in "something to do", and that gets done in the method (or is used to "do something" during a later process) you're talking Strategy. Also -- the actual invocation usually happens.

Note that the exact same code could be either -- it's really about how you're thinking about the problem and how you want others to think about it.

Answer 7

Your question is very general, and the most general answer I can think of is to use polymorphism when you have a problem requiring a callback.

Polymorphism allows you to specify a software contract in form of an interface (or an abstract class) about how your callback is to be used. Then clients are free to choose any implementation of the interface they see fit for their purpose.

Whether it is advisable to use the state, strategy, observer pattern or something completely different really depends on the circumstances.

Answer 8

I agree with the other posters about the Observer pattern as well. It's specifically designed for this purpose.