This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line!
See this thread for details.
The moose likes OO, Patterns, UML and Refactoring and the fly likes flyweight pattern Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "flyweight pattern" Watch "flyweight pattern" New topic

flyweight pattern

abalfazl hossein
Ranch Hand

Joined: Sep 06, 2007
Posts: 635

If I use the flyweight pattern so that I only store unique Time instances, I can reduce the maximum number of typical time objects to 96 (24 hours times four possible times per hour). The appointment application will still support odd times, but predictable use suggests that flyweight will dramatically minimize object creation and memory usage.

When we use flyweight we share common data between objects,Which data in these objects iin this example are similar that he share?

May you give me a simple example by code about flyweight?
Thanks in advance!

I agree. Here's the link:
subject: flyweight pattern
It's not a secret anymore!