gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
java-design-patterns/dirty-flag
History
Anurag Agarwal f2c91eb836 Resolves checkstyle errors for delegation dependency-injection dirty-flag double-buffer double-checked-locking double-dispatch (#1068) 
* Reduces checkstyle errors in delegation

* Reduces checkstyle errors in dependency-injection

* Reduces checkstyle errors in dirty-flag

* Reduces checkstyle errors in double-buffer

* Reduces checkstyle errors in double-checked-locking

* Reduces checkstyle errors in double-dispatch
2019-11-10 19:31:19 +02:00
..
etc
Fixes based on code review feedback
2018-05-12 17:47:03 +01:00
src
Resolves checkstyle errors for delegation dependency-injection dirty-flag double-buffer double-checked-locking double-dispatch (#1068)
2019-11-10 19:31:19 +02:00
pom.xml
Update license headers
2019-10-12 20:05:54 +03:00
README.md
Updated incorrect tag
2018-05-16 12:36:17 +05:30

README.md

layout, title, folder, permalink, categories, tags
layout title folder permalink categories tags
pattern Dirty Flag dirty-flag /patterns/dirty-flag/ Other
Java
Difficulty-Beginner
Performance

Intent

To avoid expensive re-acquisition of resources. The resources retain their identity, are kept in some fast-access storage, and are re-used to avoid having to acquire them again.

alt text

Applicability

Use the Dirty Flag pattern when

  • Repetitious acquisition, initialization, and release of the same resource causes unnecessary performance overhead.

Credits