netty5

History

时无两丶 28f9136824 Replace ConcurrentHashMap at allLeaks with a thread-safe set (#8467 ) Motivation: allLeaks is to store the DefaultResourceLeak. When we actually use it, the key is DefaultResourceLeak, and the value is actually a meaningless value. We only care about the keys of allLeaks and don't care about the values. So Set is more in line with this scenario. Using Set as a container is more consistent with the definition of a container than Map. Modification: Replace allLeaks with set. Create a thread-safe set using 'Collections.newSetFromMap(new ConcurrentHashMap<DefaultResourceLeak<?>, Boolean>()).'	2018-11-06 11:21:56 +01:00
..
main	Replace ConcurrentHashMap at allLeaks with a thread-safe set (#8467 )	2018-11-06 11:21:56 +01:00
test	Log the correct line-number when using SLF4j with netty if possible. (#8258 )	2018-09-07 07:34:22 +02:00

时无两丶 28f9136824 Replace ConcurrentHashMap at allLeaks with a thread-safe set (#8467 )

Motivation:
allLeaks is to store the DefaultResourceLeak. When we actually use it, the key is DefaultResourceLeak, and the value is actually a meaningless value.
We only care about the keys of allLeaks and don't care about the values. So Set is more in line with this scenario.
Using Set as a container is more consistent with the definition of a container than Map.

Modification:

Replace allLeaks with set. Create a thread-safe set using 'Collections.newSetFromMap(new ConcurrentHashMap<DefaultResourceLeak<?>, Boolean>()).'

2018-11-06 11:21:56 +01:00

main

Replace ConcurrentHashMap at allLeaks with a thread-safe set (#8467 )

2018-11-06 11:21:56 +01:00

test

Log the correct line-number when using SLF4j with netty if possible. (#8258 )

2018-09-07 07:34:22 +02:00