On Wednesday 28 Nov 2007, Aldo Bucchi wrote:
cummulative distinct persons, but each one is used only for a couple
of minutes and won't occur again.
Why not delete it all together then ?
--
Tom Chiverton
Helping to ambassadorially develop clicks-and-mortar clusters
on:
Hi Tom,
Because I would only like to delete those that are not in use... just
like Garbage Collection. If I just removed every reference I could not
achieve identity allocation ( which is a requirement ).
To clarify:
Suppose you are coding an email user interface, like GMail, where
there are
On Thursday 29 Nov 2007, Aldo Bucchi wrote:
While some of these emails will surface constantly at the user
interface ( while reading a thread ) others will only be used for mere
seconds and will never appear again. It makes sense to remove the
latter from memory... specially when we are
Yes, get your point... but that won´t solve it either.
( Sorry, I am having trouble expressing myself. ( I am still up after
an all nighter ) )
Use a Timer to flush objects with timestamps more then $TIME ago.
Ok, suppose I flush the objects in the cache ( within the factory ).
And then an
On Thursday 29 Nov 2007, Aldo Bucchi wrote:
Yes, get your point... but that won´t solve it either.
K, now where getting into the meat of it :-)
Use a Timer to flush objects with timestamps more then $TIME ago.
Ok, suppose I flush the objects in the cache ( within the factory ).
And then an
Hi all,
I have a situation where I need to pool a certain type of objects
based on their value, so that for each for each person ID I have at
most one PersonVO living at a certain moment
This way I can always test equality as follows:
personVO1 === personVO2
instead of a custom value based
6 matches
Mail list logo
