Modular library
From APIDesign
(Difference between revisions)
(New page: In contrast to simple library, the modular one is ready for being extended. It contains API, but often it requires (or allows) someone else to provide useful implementation. Classi...) |
|||
| Line 1: | Line 1: | ||
| - | In contrast to [[simple library]], the modular one is ready for being extended. It contains [[API]], but often it requires (or allows) someone else to provide useful implementation. Classical example can be javax.xml.DocumentBuilderFactory which just defines the [[API]] but allows others to plug in various implementations of the [[XML]] parsers. | + | In contrast to [[simple library]], the modular one is ready for being extended. It contains [[API]], but often it requires (or allows) someone else to provide useful implementation. Classical example can be javax.xml.DocumentBuilderFactory which just defines the [[API]] but allows others to plug in various implementations of the [[XML]] parsers (and requires at least one provider to be present). |
Revision as of 05:19, 14 April 2011
In contrast to simple library, the modular one is ready for being extended. It contains API, but often it requires (or allows) someone else to provide useful implementation. Classical example can be javax.xml.DocumentBuilderFactory which just defines the API but allows others to plug in various implementations of the XML parsers (and requires at least one provider to be present).
Follow
