2018-02-20 09:48:44 +00:00
|
|
|
---
|
|
|
|
layout: pattern
|
|
|
|
title: Dirty Flag
|
|
|
|
folder: dirty-flag
|
|
|
|
permalink: /patterns/dirty-flag/
|
|
|
|
categories: Other
|
|
|
|
tags:
|
|
|
|
- Java
|
2018-05-16 12:36:17 +05:30
|
|
|
- Difficulty-Beginner
|
2018-02-20 09:48:44 +00:00
|
|
|
- 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.
|
|
|
|
|
|
|
|

|
|
|
|
|
|
|
|
## Applicability
|
|
|
|
Use the Dirty Flag pattern when
|
|
|
|
|
|
|
|
* Repetitious acquisition, initialization, and release of the same resource causes unnecessary performance overhead.
|
|
|
|
|
|
|
|
## Credits
|
|
|
|
|
|
|
|
* [Design Patterns: Dirty Flag](https://www.takeupcode.com/podcast/89-design-patterns-dirty-flag/)
|