gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
java-design-patterns/dirty-flag
History
Anurag Agarwal ea57934db6 Java 11 migrate c-d (remaining) (#1111) 
* Moves converter pattern to Java 11

* Moves cqrs pattern to Java 11

* Moves dao pattern to Java 11

* Moves data-bus pattern to Java 11

* Moves data-locality pattern to Java 11

* Moves data-mapper pattern to Java 11

* Moves data-transfer-object pattern to Java 11

* Moves decorator pattern to Java 11

* Moves delegation pattern to Java 11

* Moves dependency-injection to Java 11

* Moves dirty-flag to Java 11

* Moves double-buffer to Java 11

* Moves double-checked-locking to Java 11

* Moves double-dispatch to Java 11

* Corrects with changes thats breaking test cases
2019-12-14 20:32:45 +02:00
..
etc
#1113 Add uml-reverse-mapper plugin
2019-12-07 18:03:49 +02:00
src
Java 11 migrate c-d (remaining) (#1111)
2019-12-14 20:32:45 +02:00
pom.xml
Set version for next development iteration
2019-11-17 14:45:41 +02:00
README.md
https://github.com/iluwatar/java-design-patterns-web/issues/8 Update pattern categories and tags
2019-12-13 21:09:28 +02:00

README.md

layout, title, folder, permalink, categories, tags
layout title folder permalink categories tags
pattern Dirty Flag dirty-flag /patterns/dirty-flag/ Behavioral
Game programming
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.

Class diagram

alt text

Applicability

Use the Dirty Flag pattern when

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

Credits