Hubbry Logo
search button
Sign in
Implicit invocation
Implicit invocation
Comunity Hub
History
arrow-down
starMore
arrow-down
bob

Bob

Have a question related to this hub?

bob

Alice

Got something to say related to this hub?
Share it here.

#general is a chat channel to discuss anything related to the hub.
Hubbry Logo
search button
Sign in
Implicit invocation
Community hub for the Wikipedia article
logoWikipedian hub
Welcome to the community hub built on top of the Implicit invocation Wikipedia article. Here, you can discuss, collect, and organize anything related to Implicit invocation. The purpose of the hub is to c...
Add your contribution
Implicit invocation

Implicit invocation is a term used by some authors for a style of software architecture in which a system is structured around event handling, using a form of callback. It is closely related to inversion of control and what is known informally as the Hollywood principle.

The idea behind implicit invocation is that instead of invoking a procedure directly, a component can announce (or broadcast) one or more events. Other components in the system can register an interest in an event by associating a procedure with the event. When the event is announced the system itself invokes all of the procedures that have been registered for the event. Thus an event announcement implicitly causes the invocation of procedures in other modules.

— David Garlan and Mary Shaw, "An Introduction to Software Architecture"[1]

Implicit invocation is the core technique behind the observer pattern.[citation needed]

See also

[edit]

References

[edit]
  1. ^ Garlan, David; Shaw, Mary (1994). An Introduction to Software Architecture (PDF).
[edit]