2009/2/9 je...@swank.ca
>
> I've tagged a new snapshot and uploaded new binaries for a new
> prerelease. This is a preview of Guice 2. Since the previous 20081123
> snapshot, we've improved servlets, private modules, assisted inject
> and performance. This .zip includes the guice jar, extension j
congratulations jesse and thanks for all your hard work. =)
On Mon, Feb 9, 2009 at 7:37 AM, je...@swank.ca wrote:
>
> I've tagged a new snapshot and uploaded new binaries for a new
> prerelease. This is a preview of Guice 2. Since the previous 20081123
> snapshot, we've improved servlets, privat
I've tagged a new snapshot and uploaded new binaries for a new
prerelease. This is a preview of Guice 2. Since the previous 20081123
snapshot, we've improved servlets, private modules, assisted inject
and performance. This .zip includes the guice jar, extension jars, and
javadoc:
http://google-g
This was just an update to the new API (MapMaker in place of
ReferenceCache). I still need to address the issues w/ security contexts and
inheritable thread locals.
I think I can resolve the security reference by starting the thread in a
doPriveleged() wrapper.
I plan to use reflection to null ou
Weekly Nascar Pocket Guide
http://nascar.bloggerhelp.cn/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"google-guice" group.
To post to this group, send email to google-guice@googlegroups.com
To unsubscribe from t
I began this discussion thread because in revision 830 Bob committed
changes with a description "Replace ReferenceCache w/ MapMaker". It's
not clear what really changed between ReferenceCache and MapMaker. If
you take a look at MapMaker, FinalizableReferenceQueue and Finalizer it
look
2009/2/8 Gili
>
> Stuart,
>
> It was my understanding [1] that there was no need for a worker
> thread. I thought that we had established that there were concurrent
> reference map implementations out there that will do a great job
> without it and one of them might even end up in Java7 (all the
Stuart,
It was my understanding [1] that there was no need for a worker
thread. I thought that we had established that there were concurrent
reference map implementations out there that will do a great job
without it and one of them might even end up in Java7 (all the better
since we'd end up usi
Unlimited Wii Downloads! Wii Games, Wii Music & Much More!
http://wii.bloggerhelp.cn/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"google-guice" group.
To post to this group, send email to google-guice@googlegro
2009/2/7 Gili
> Hi,
>
> I noticed you guys committed some new code to tackle the memory leaks
> recently so I gave it a spin. I still see the memory leak under
> Glassfish v2ur2 and the GC root that is keeping the instances alive
> seems to be com.google.inject.internal.Finalizer.
>
> Stuart, can
10 matches
Mail list logo