|
Pool vs Cache Note to myself Programming and Design, 090730 Put stateless objects, most likely mutables, which must be acquired and released, in a pool. Put stateful objects, likely immutables in a cache. Objects acquired from a pool will have to be released before they can be acquired again, thus only one can have reference to the object. But from the cache everyone can get a reference to the desired object at any time, without any restrictions, thus many can have reference to the same object and a object get from cache does not have to be released. From a pool it does not matter which object you get. From a cache, which object you gets make all the difference in the world. - Aramis 
  |
Personal Blog of Aramis Welcome. Filter: Show all, Personal, Programming & Design, Spirit, Economics. There is no particular goal to this blog, but to convey what I find interesting and worth writing about. Get blog as RSS or ATOM  .
I never update my twitter feed.
Drive-By Distributed Computing
100218
The Dream Machine
091031
My first GA
091010
Hyper Media
090909
GPS Tag Your Site
090809
OO Instead of Flags
090803
Pool vs Cache
090730
GUI Programming
090704
Brain Computer
081223
Softcoding and Utilities
081115
Throwaway Apps
081027
HTC Dream
081004
J2ME Extends
080911
123
080730
Collaboration
080719
3H Listener
080711
Agent Scripting
080707
Biological Mechanisms
080609
Transitions and GUI
080531
Semantic GUI
080530
Breathing GUI
080529
Diggin
080525
|
||