This HTML5 document contains 52 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
dcthttp://purl.org/dc/terms/
yago-reshttp://yago-knowledge.org/resource/
dbohttp://dbpedia.org/ontology/
foafhttp://xmlns.com/foaf/0.1/
n12http://dbpedia.org/resource/File:
dbthttp://dbpedia.org/resource/Template:
rdfshttp://www.w3.org/2000/01/rdf-schema#
freebasehttp://rdf.freebase.com/ns/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
n9http://en.wikipedia.org/wiki/
dbchttp://dbpedia.org/resource/Category:
provhttp://www.w3.org/ns/prov#
dbphttp://dbpedia.org/property/
xsdhhttp://www.w3.org/2001/XMLSchema#
goldhttp://purl.org/linguistics/gold/
dbrhttp://dbpedia.org/resource/

Statements

Subject Item
dbr:Observer_pattern
rdf:type
dbo:Disease
rdfs:label
Observer pattern
rdfs:comment
The observer pattern is a software design pattern in which an object, named 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.
owl:sameAs
yago-res:Observer_pattern freebase:m.015yvb
dbp:wikiPageUsesTemplate
dbt:Design_Patterns_Patterns dbt:Wikibooks-inline dbt:Code dbt:Reflist
dct:subject
dbc:Software_design_patterns dbc:Articles_with_example_Java_code dbc:Articles_with_example_Python_(programming_language)_code dbc:Articles_with_example_C_Sharp_code
gold:hypernym
dbr:Pattern
prov:wasDerivedFrom
n9:Observer_pattern?oldid=1070267312&ns=0
dbo:wikiPageID
164863
dbo:wikiPageLength
20657
dbo:wikiPageRevisionID
1070267312
dbo:wikiPageWikiLink
dbr:Entity_component_system dbr:Software_design_pattern dbr:Memory_leak dbr:Python_(programming_language) dbr:Lapsed_listener_problem dbr:Object_(computer_science) dbr:Scalability dbc:Articles_with_example_Python_(programming_language)_code dbr:Weak_reference dbc:Articles_with_example_Java_code dbr:Method_(computer_programming) dbr:Implicit_invocation dbr:Java_(programming_language) dbc:Software_design_patterns n12:Observer_w_update.svg dbr:Class_diagram dbr:Event_(computing) dbc:Articles_with_example_C_Sharp_code dbr:Epoll dbr:Mediator_pattern dbr:Publish–subscribe_pattern dbr:Client–server_model dbr:Multiprocessing dbr:Unified_Modeling_Language dbr:Sequence_diagram dbr:Painter's_algorithm dbr:Singleton_pattern n12:W3sDesign_Observer_Design_Pattern_UML.jpg dbr:Design_Patterns dbr:Dispose_pattern dbr:Polling_(computer_science) dbr:Progress_bar
dbo:abstract
The observer pattern is a software design pattern in which an object, named 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 for implementing distributed event handling systems, in "event driven" software. In those systems, the subject is usually named a "stream of events" or "stream source of events", while the observers are called "sinks of events". The stream nomenclature alludes to a physical setup where the observers are physically separated and have no control over the emitted events from the subject/stream-source. This pattern then perfectly suits any process where data arrives from some input that is not available to the CPU at startup, but instead arrives "at random" (HTTP requests, GPIO data, user input from keyboard/mouse/..., distributed databases and blockchains, ...). Most modern programming-languages comprise built-in "event" constructs implementing the observer-pattern components. While not mandatory, most 'observers' implementations would use background threads listening for subject-events and other support mechanisms provided by the kernel (Linux epoll, ...).
foaf:isPrimaryTopicOf
n9:Observer_pattern