Openfire

All classes that are likely to be cached should be immutable.

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 3.6.4
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Acceptance Test - Add?:
    No

Description

Cached objects that are immutable can cause weird problems, if references are updated after the object has been cached. Instead, use immutable objects (the JCIP annotations can help here).

As a bonus, we will prevent most concurrency-related problems when we make stuff immutable.

Activity

There are no comments yet on this issue.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated: