[ 
https://issues.apache.org/jira/browse/DBCP-578?focusedWorklogId=604255&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-604255
 ]

ASF GitHub Bot logged work on DBCP-578:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 31/May/21 18:53
            Start Date: 31/May/21 18:53
    Worklog Time Spent: 10m 
      Work Description: arturobernalg commented on pull request #101:
URL: https://github.com/apache/commons-dbcp/pull/101#issuecomment-851635811


   > Hi @arturobernalg
   > 
   > Why? You need a clear explanation of why `Collections.synchronizedList` is 
better than `Vector` or `CopyOnWriteArrayList`.
   > Can changing this be likely to have ramification beyond what the current 
tests assert?
   > I plan on cutting a release candidate very soon so this one might have to 
wait for the next go around.
   
   Hi @garydgregory 
   We won using the List interface and all the implementations. We don't lose 
the synchronized behavior because it create by Collections.synchronizedList.
   And seems logical --> https://stackoverflow.com/a/1386288/4495592
   Maybe I'm wrong.
   TY


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 604255)
    Time Spent: 0.5h  (was: 20m)

> Use List Instead Of Vector
> --------------------------
>
>                 Key: DBCP-578
>                 URL: https://issues.apache.org/jira/browse/DBCP-578
>             Project: Commons DBCP
>          Issue Type: Sub-task
>            Reporter: Arturo Bernal
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> ArrayList is a much better Collection implementation than Vector 
> I'm going to use Collections.synchronizedList since Vectors are thread-safe



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to