Lazy loading can lead to stale data, violates IoC?

Trying to be a better programmer

Why does this static field always get initialized over-eagerly?

I am looking at this excellent article from Jon Skeet.

Is ‘lazy’ the correct term for timestamp-based skipping? [closed]

Closed 9 years ago.

Is ‘lazy’ the correct term for timestamp-based skipping? [closed]

Closed 9 years ago.

Is ‘lazy’ the correct term for timestamp-based skipping? [closed]

Closed 9 years ago.

Is ‘lazy’ the correct term for timestamp-based skipping? [closed]

Closed 9 years ago.

Is ‘lazy’ the correct term for timestamp-based skipping? [closed]

Closed 9 years ago.

Does laziness yield more race conditions?

I recently ran into a race condition while accessing a configuration setting. After examining what I could of the code, I came to the conclusion that the Configuration class’ laziness¹ was the source of the race condition. Pondering that lead me to me wonder if laziness naturally yields a greater chance of race conditions?

Does a create() method exist as part of a pattern? [closed]

Closed 9 years ago.

Applying initialization-on-demand holder idiom at variable level rather than class

I was looking for the idiomatic way to implement thread-safe lazy initialization for a configuration collection retrieved from the DB inside a Spring bean.