RE: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-10-01 Thread Josh Fenlason
the end of October at the latest so I can avoid having to do my own fork of the library. Thanks, Josh. -Original Message- From: Josh Fenlason Sent: Wednesday, September 25, 2024 3:25 PM To: Commons Developers List Subject: RE: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

RE: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-09-25 Thread Josh Fenlason
Sounds good. I'll keep an eye out for it. -Original Message- From: Gary Gregory Sent: Wednesday, September 25, 2024 3:22 PM To: Commons Developers List Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap CAUTION: This email originated from outside the organiz

Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-09-25 Thread Gary Gregory
-- > From: Gary Gregory > Sent: Wednesday, September 25, 2024 2:52 PM > To: Commons Developers List > Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap > > > CAUTION: This email originated from outside the organization. Do not click > links or open attac

RE: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-09-25 Thread Josh Fenlason
Excellent, thanks for that encouraging update! Is there anything I can assist with? Josh. -Original Message- From: Gary Gregory Sent: Wednesday, September 25, 2024 2:52 PM To: Commons Developers List Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap CAUTION

Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-09-25 Thread Gary Gregory
> Thanks, > Josh. > > -Original Message- > From: Gary Gregory > Sent: Monday, September 16, 2024 4:26 PM > To: Commons Developers List > Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap > > > CAUTION: This email originated from outs

RE: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-09-25 Thread Josh Fenlason
x27;s PR and wrap up this issue? Thanks, Josh. -Original Message- From: Gary Gregory Sent: Monday, September 16, 2024 4:26 PM To: Commons Developers List Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap CAUTION: This email originated from outside the organization. Do

Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-09-16 Thread Gary Gregory
nk it ok...so Gary which part do you feel unsafe in it ?I must >> admit I am not that familiar to lawyer things.. >> >> From: Melloware Inc >> Sent: Saturday, September 14, 2024 9:18:08 PM >> To: Commons Developers List >> Subject: R

Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-09-16 Thread Gary Gregory
m: Melloware Inc > Sent: Saturday, September 14, 2024 9:18:08 PM > To: Commons Developers List > Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap > > Well in my PR the license in the file says this. > > Written by Doug Lea with assistance from members o

Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-09-14 Thread Xeno Amess
4, 2024 8:32:38 PM > To: Commons Developers List > Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap > > I submitted this PR years ago using ConcurrentWeakKeyHashMap from Doug Lea > and the Netty team but Gary had concerns from legal about being able to use > it.

Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-09-14 Thread Melloware Inc
o: Commons Developers List > Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap > > I submitted this PR years ago using ConcurrentWeakKeyHashMap from Doug Lea > and the Netty team but Gary had concerns from legal about being able to use > it. > > PR is here: http

Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-09-14 Thread Xeno Amess
mmons Developers List > Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap > > On Thu, 12 Sep 2024 at 19:59, Gary D. Gregory wrote: > > > Hi All, > > > > For the upcoming 2.0.0-M1, I plan on replacing the custom WeakFastHashMap > > with the stock C

Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-09-14 Thread Melloware Inc
Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap > > On Thu, 12 Sep 2024 at 19:59, Gary D. Gregory wrote: > > > Hi All, > > > > For the upcoming 2.0.0-M1, I plan on replacing the custom WeakFastHashMap > > with the stock ConcurrentHashMap. &g

Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-09-14 Thread Xeno Amess
: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap On Thu, 12 Sep 2024 at 19:59, Gary D. Gregory wrote: > Hi All, > > For the upcoming 2.0.0-M1, I plan on replacing the custom WeakFastHashMap > with the stock ConcurrentHashMap. > > If you think this is a bad idea,

Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-09-14 Thread Xeno Amess
good and should did it 5 years ago From: Niall Pemberton Sent: Saturday, September 14, 2024 1:46:32 PM To: Commons Developers List Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap On Thu, 12 Sep 2024 at 19:59, Gary D. Gregory wrote: >

Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-09-13 Thread Niall Pemberton
On Thu, 12 Sep 2024 at 19:59, Gary D. Gregory wrote: > Hi All, > > For the upcoming 2.0.0-M1, I plan on replacing the custom WeakFastHashMap > with the stock ConcurrentHashMap. > > If you think this is a bad idea, please tell us why. It’s a good idea for the “fast” part, but the “weak” aspect a

RE: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-09-12 Thread Josh Fenlason
I concur. -Original Message- From: Melloware Inc Sent: Thursday, September 12, 2024 12:25 PM To: Commons Developers List Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap CAUTION: This email originated from outside the organization. Do not click links or open

Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap

2024-09-12 Thread Melloware Inc
I think this is a good idea. On Thu, Sep 12, 2024 at 1:00 PM Gary D. Gregory wrote: > Hi All, > > For the upcoming 2.0.0-M1, I plan on replacing the custom WeakFastHashMap > with the stock ConcurrentHashMap. > > If you think this is a bad idea, please tell us why. > > Gary > > --