Re: LinearProbeHashtable Re: ClassValue perf?

2016-05-27 Thread Paul Sandoz
Hi Peter, > On 27 May 2016, at 12:41, Peter Levart wrote: > > Hi Paul, > > On 05/26/2016 01:20 PM, Paul Sandoz wrote: >> Hi Peter, >> >> Opportunistically if your LinearProbeHashtable works out then i am wondering >> if we could replace the use of CHM within >> MethodType.ConcurrentWeakInter

Re: proxy an interface and call a default method

2016-05-27 Thread Remi Forax
I don't see the issue if the lookup object represent the proxy class itself restricted to only access to public methods. Rémi - Mail original - > De: "Peter Levart" > À: "Da Vinci Machine Project" , "jochen Theodorou" > > Envoyé: Vendredi 27 Mai 2016 12:50:34 > Objet: Re: proxy an in

Re: proxy an interface and call a default method

2016-05-27 Thread Peter Levart
Hi, I think the main problem here is that by providing the InvocationHandler with a Lookup that could provide "invokespecial" MHs for the proxy interface(s) could be abused. Anyone can create a Proxy for any public interface and supply its own InvocationHandler which could be used to "steal"

Re: LinearProbeHashtable Re: ClassValue perf?

2016-05-27 Thread Peter Levart
Hi Paul, On 05/26/2016 01:20 PM, Paul Sandoz wrote: Hi Peter, Opportunistically if your LinearProbeHashtable works out then i am wondering if we could replace the use of CHM within MethodType.ConcurrentWeakInternSet, which only uses get/putIfAbsent/remove. Thereby CHM can use VarHandles wit