Jump to content

Object pool pattern: Revision history


For any version listed below, click on its date to view it. For more help, see Help:Page history and Help:Edit summary. (cur) = difference from current version, (prev) = difference from preceding version, m = minor edit, → = section edit, ← = automatic edit summary

(newest | oldest) View (newer 50 | ) (20 | 50 | 100 | 250 | 500)

30 April 2025

15 November 2024

3 July 2023

1 July 2023

9 October 2022

25 May 2022

3 December 2021

30 September 2021

16 March 2021

26 February 2021

25 February 2021

26 January 2021

14 December 2020

25 November 2020

25 August 2020

  • curprev 12:1112:11, 25 August 2020 86.156.195.218 talk 18,844 bytes −376 The linked reference I removed does not mention object pools at all. The following article in the series (https://www.ibm.com/developerworks/java/library/j-jtp01274/index.html?ca=drs-) does not say to *never* use object pooling in Java undo Tag: references removed

15 May 2020

11 May 2020

8 April 2020

13 March 2020

13 February 2020

3 February 2020

21 August 2019

4 August 2018

10 January 2018

24 April 2017

  • curprev 12:2712:27, 24 April 2017 Vip saran talk contribs m 16,442 bytes +144 Java code example: fixed methods visibility, case in getObject() when all available PooledObjects have expired and removed unnecessary cleaning of objects returned from the available map (which only has clean objects) undo

19 November 2016

4 November 2016

26 September 2016

17 September 2016

4 May 2016

15 April 2016

23 October 2015

25 September 2015

18 September 2015

1 August 2015

14 July 2015

29 April 2015

27 April 2015

24 April 2015

25 March 2015

2 December 2014

1 December 2014

  • curprev 21:4321:43, 1 December 2014 159.45.129.17 talk 13,682 bytes −579 Reversed the main premise of this passage. Automated object pools are possible in C++ via smart pointers; Only manual possible in Java/C# as finalizers are really a bad idea. undo
(newest | oldest) View (newer 50 | ) (20 | 50 | 100 | 250 | 500)