Files
java-design-patterns/dirty-flag
Robert Volkmann 465a6871b2 dependencies: Upgrade mockito 3.5 to 4.5 (#2316)
* refactor: move tests of leader-followers into correct package

* dep: remove version constraint for Mockito in acyclic-visitor

* dep: remove version constraint for Mockito in caching

* chore: cleanup mockito-core import on some POMs

* dep: upgrade core.mocktio 3.5.6 to 4.5.1

"- org.mockito.Mockito#verifyZeroInteractions an alias of verifyNoMoreInteractions"
https://github.com/mockito/mockito/commit/caf35b24e2764df0498469526ecb3e7ec68a0430
2022-11-20 10:16:53 +02:00
..
2019-12-07 18:03:49 +02:00
2022-09-14 23:22:24 +05:30

title, category, language, tags
title category language tags
Dirty Flag Behavioral en
Game programming
Performance

Also known as

  • IsDirty pattern

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